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.
Tom
On 3/1/2011 6:52 AM, thomas_at_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?
>
> Thomas
>