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 6:27:00 am
List:net.java.dev.glassfish.users

I tried it:  

snip

$asadmin enable-secure-admin domain1 It appears that server [localhost:4848] accepts secure connections only. Retrying the command with --secure=true... java.net.SocketException: Unexpected end of file from server Command enable-secure-admin failed. $asadmin --secure=true enable-secure-admin domain1 Enter admin user name>  admin Enter admin password for user "admin"> Command enable-secure-admin not found. Check the entry of command name. This command may be provided by a package that
is not installed. Command enable-secure-admin failed.  

snip

  It would be nice if GF would say *which* package provides this command!   Thomas

Anissa Lam <anis@oracle.com> hat am 1. März 2011 um 17:35 geschrieben:

You mentioned starting the domain with --secure option.

asadmin --secure=true start-domain domain1

does not come back.

I am not sure if --secure=true does the exact same thing as running 'enable-secure-admin' command which requires server restart. How about running the enable-secure-admin command instead ?  Something like:

- asadmin start-domain domain1 - asadmin enable-secure-admin domain1 - asadmin stop-domain domain1 - asadmin start-domain domain1

and see if that makes any different.

Anissa.

On 3/1/11 7: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?