On 4/28/09 6:15 PM, Jonathan Benoit wrote:
> i see only one instance of server running. the server started as
> shown by the process id output below. why did it take so long to
> start as to have to display this message,
Something is wrong in your env...other processes using ports, network
setup error (highly possible, causing long timeouts), env variables,
file corruption, zip install corruption, bad build, cosmic dust, memory
error, whatever...
> and what does one expect to see in server.log to confirm that server
> started when we do see this 90 second message?
for example: INFO: GlassFish v3 startup time : Felix(4181ms) startup
services(3696ms) total(7877ms)
or use the server (admin server, cli, ...) to see if you really have a
responding server.
I see no problems with my private builds, so look elsewhere than the
server itself.
Sometimes, a reboot helps.
Also, jdk1.6.04 is quite old:-)
Ludo
>
> On 04/28/09 20:19, Jane Young wrote:
>> Do you have another instance of server running? I can start with no
>> issue.
>>
>>
>> Jonathan Benoit wrote:
>>> i'm using Glassfish V3 nightly build
>>> (glassfish-v3-b47-04_27_2009.zip) and i see this message trying to
>>> start Glassfish:
>>>
>>> % ./asadmin start-domain domain1
>>>
>>> Domain (domain1) did not respond in 90 seconds. It means it is still
>>> coming up or it has failed to come up. Check server.log for details.
>>>
>>> I see nothing in server.log to indicate it failed to come up, nor do
>>> i see any confirmation that server successfully started. I checked
>>> ps output and i do see process started:
>>>
>>> 24195 pts/6 S 0:21 /usr/jdk/jdk1.6.0_04/bin/java -cp
>>> /glassfishv3/glassfish/modules/glassfish.jar
>>> -XX:+UnlockDiagnosticVMOptions -XX:MaxPermSize=192m -XX:NewRatio=2
>>> -XX:+LogVMOutput
>>> -XX:LogFile=/glassfishv3/glassfish/domains/domain1/logs/jvm.log
>>> -Xmx512m -client -Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
>>> -Djavax.net.ssl.trustStore=/glassfishv3/glassfish/domains/domain1/config/cacerts.jks
>>> -Djavax.net.ssl.keyStore=/glassfishv3/glassfish/domains/domain1/config/keystore.jks
>>> -Djava.security.policy=/glassfishv3/glassfish/domains/domain1/config/server.policy
>>> -Dcom.sun.enterprise.security.httpsOutboundKeyAlias=s1as
>>> -Dcom.sun.aas.instanceRoot=/glassfishv3/glassfish/domains/domain1
>>> -Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
>>> -DWSIT_HOME=/glassfishv3/glassfish
>>> -Djava.security.auth.login.config=/glassfishv3/glassfish/domains/domain1/config/login.conf
>>> -Djava.endorsed.dirs=/glassfishv3/glassfish/lib/endorsed
>>> -Dcom.sun.aas.installRoot=/glassfishv3/glassfish
>>> -Djava.ext.dirs=/usr/jdk/jdk1.6.0_04/lib/ext:/usr/jdk/jdk1.6.0_04/jre/lib/ext:/glassfishv3/glassfish/domains/domain1/lib/ext:/glassfishv3/javadb/lib
>>> com.sun.enterprise.glassfish.bootstrap.ASMain -domainname domain1
>>> -asadmin-args start-domain,,,domain1 -instancename server -verbose
>>> false -debug false -asadmin-classpath ./../modules/admin-cli.jar
>>> -asadmin-classname com.sun.enterprise.admin.cli.AsadminMain
>>> -domaindir /glassfishv3/glassfish/domains/domain1
>>>
>>> why do i see this message, (90 seconds seems like a long time to
>>> wait for startup) and should I see a message in server.log
>>> confirming that server did indeed start?
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>