atom feed16 messages in net.java.dev.glassfish.usersRe: upgrade problem
FromSent OnAttachments
tho...@randspringer.deMar 1, 2011 4:52 am 
Tom MuellerMar 1, 2011 7:12 am 
tho...@randspringer.deMar 1, 2011 7:54 am 
Tim QuinnMar 1, 2011 8:11 am 
tho...@randspringer.deMar 1, 2011 8:19 am 
Anissa LamMar 1, 2011 8:34 am 
tho...@randspringer.deMar 2, 2011 5:15 am 
tho...@randspringer.deMar 2, 2011 6:27 am 
rjfengMar 2, 2011 7:04 am 
Martin GaintyMar 2, 2011 11:12 am 
Snjezana Sevo-ZenzerovicMar 2, 2011 11:57 am 
rjfengMar 2, 2011 7:29 pm 
tho...@randspringer.deMar 4, 2011 8:17 am 
BAMOSSMar 4, 2011 9:12 am 
tho...@randspringer.deMar 7, 2011 1:24 am 
bam...@sceats.comMar 9, 2011 10:19 am 
Subject:Re: upgrade problem
From:tho...@randspringer.de (tho@randspringer.de)
Date:Mar 2, 2011 5:15:09 am
List:net.java.dev.glassfish.users

Hi,

I run now

  java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)   I removed the -Dsun.security.ssl.allowUnsafeRenegotiation=true property from
domain.xml stopped the server and startet it again.   The server started without error messages. But when I access the admin-console
via https I get a lot of exceptions.   [#|2011-03-02T13:28:34.149+0100|SEVERE|glassfish3.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=24;_ThreadName=Thread-1;|service
exception java.lang.RuntimeException: ClientAbortException:  java.io.IOException:
SSLOutputWriter: CLOSED         at
org.glassfish.admin.rest.LazyJerseyInit.reportError(LazyJerseyInit.java:200)         at
org.glassfish.admin.rest.adapter.RestAdapter.reportError(RestAdapter.java:453)         at
org.glassfish.admin.rest.adapter.RestAdapter.service(RestAdapter.java:209)   The full jvm.log and server.log is here:   http://www.randspringer.de/jvm.log http://www.randspringer.de/server.log   I see a lot of dependency errors in jvm.log. Which packages are necessary to run
GF as pure servlet container. We need it for 3 WARs: 1. our own rails-application-WAR 2. hudson WAR 3. apache-solr-WAR     pkg list gives:   NAME (PUBLISHER)                              VERSION         STATE      UFIX felix                                         3.0.8-0         installed  ---- glassfish-appclient                           3.1-43          installed  ---- glassfish-common                              3.1-43          installed  ---- glassfish-common-full                         3.1-43          installed  ---- glassfish-corba                               3.1.0-27        installed  ---- glassfish-corba-base                          3.1.0-27        installed  ---- glassfish-ejb                                 3.1-43          installed  ---- glassfish-ejb-lite                            3.1-43          installed  ---- glassfish-full-incorporation                  3.1-43          installed  ---- glassfish-grizzly                             1.9.31-1        installed  ---- glassfish-grizzly-full                        1.9.31-1        installed  ---- glassfish-gui                                 3.1-43          installed  ---- glassfish-hk2                                 3.1-43          installed  ---- glassfish-jca                                 3.1-43          installed  ---- glassfish-jcdi                                3.1-43          installed  ---- glassfish-jdbc                                3.1-43          installed  ---- glassfish-jpa                                 3.1-43          installed  ---- glassfish-jsf                                 2.1.0-11        installed  ---- glassfish-jta                                 3.1-43          installed  ---- glassfish-jts                                 3.1-43          installed  ---- glassfish-management                          3.1-43          installed  ---- glassfish-nucleus                             3.1-43          installed  ---- glassfish-registration                        3.1-43          installed  ---- glassfish-scripting                           3.1-41          installed  ---- glassfish-web                                 3.1-43          installed  ---- glassfish-web-incorporation                   3.1-43          installed  ---- javadb-client                                 10.6.2.1-1      installed  ---- javadb-common                                 10.6.2.1-1      installed  ---- javadb-core                                   10.6.2.1-1      installed  ---- jersey                                        1.5-1.0         installed  ---- metro                                         2.1-30          installed  ---- pkg                                           1.122.2-52.2817 installed  ---- pkg-java                                      1.122-52.2817   installed  ---- pkg-toolkit-incorporation                     2.3.3-52.2817   installed  ---- python2.4-minimal                             2.4.4.0-52.2817 installed  ---- shoal                                         1.5.29-0        installed  ---- updatetool                                    2.3.3-52.2817   installed  ---- wxpython2.8-minimal                           2.8.10.1-52.2817 installed  ----

Maybe I have to do some reinstallation or uninstallation?   Any help is appreciated.   Thomas    

Ok. Admin is informed. Hopefully I can report success tomorrow.

Tim Quinn <tim.@oracle.com> hat am 1. März 2011 um 17:11 geschrieben:

Hello, Thomas.

I believe that these new symptoms - as well as the ones you described  earlier - are the result of the way the Java runtime has addressed the  problem in the SSL protocol Tom mentioned earlier.

You should run Java 1.6.0_22 or later on both the client and server  side.  That is the minimum version of Java which GlassFish 3.1  requires, partly because of the SSL security issue in earlier releases  of Java.

GlassFish 3.1 and 3.0.1 are different in significant ways.  One of  them is improved security of admin traffic which requires Java  1.6.0_22 or later to work correctly, which 3.0.1 did not require.  We  do not recommend that users set the various security properties that  might allow you to use earlier releases because that leaves your  system more vulnerable.

On Mar 1, 2011, at 9:55 AM, tho@randspringer.de wrote:

Hm,

it worked with 3.0.1.

After I deinstalled some packagages(e.g. this cluster stuff) now GF  at least talked to me when I added the --verbose option.

First I got this error: http://java.net/jira/browse/GLASSFISH-12041

I added the property: -Dsun.security.ssl.allowUnsafeRenegotiation=true to my domain.xml

and now I get:

java.lang.RuntimeException: ClientAbortException:    java.io.IOException: SSLOutputWriter: CLOSED          at  org .glassfish.admin.rest.LazyJerseyInit.reportError(LazyJerseyInit.java: 200)          at  org .glassfish .admin.rest.adapter.RestAdapter.reportError(RestAdapter.java:453)          at  org .glassfish.admin.rest.adapter.RestAdapter.service(RestAdapter.java: 209)

What can I now do? I can not simply deinstall jersey because glassfish-gui and  glassfish-management depends on it.

Tom Mueller <tom.@oracle.com> hat am 1. März 2011 um 16:13  geschrieben:

I'm not sure that this is the problem, but GlassFish 3.1 running  in with secure admin enabled requires a minimum JVM version of 1.6.0_22. I  see from your jvm.log file that you are running 1.6.0_20.

There was an SSL vulnerability that was fixed in _22.  When  running with an older VM, the behavior of start-domain --secure is that it  appears to hang even though the DAS actually started, because start-domain  cannot establish a connection to the DAS to verify that it is up.

On 3/1/2011 6:52 AM, tho@randspringer.de wrote:

Hi,

today I tried to upgrade our GF 3.0.1 to 3.1. We use it only as an servlet container for our rails-application.

I upgraded via the "updatetool" (source=stable.glassfish.org).

After installing the new packages I stopped the domain and I  started it with the --upgrade option like suggested.

However now

asadmin --secure=true start-domain domain1

does not come back.

jvm.log and server.log are available from

http://www.randspringer.de/jvm.log

http://www.randspringer.de/server.log

What is the problem and how can I get the glassfish running again?