Glassfish Server Instance Startup Times Out After 20 Minutes.
Last updated on NOVEMBER 05, 2016
Applies to:Oracle GlassFish Server - Version: 9.1 to 2.1.1 - Release: 9.1 to 2.1
Information in this document applies to any platform.
Note that this is a different timeout from that which is applied when a Node Agent is being started and its also starting up its instances as part of its startup sequence, please refer to <Note:1267667.1> for further details of that use case.
This is the error seen when starting an instance from the command line, in this case the instance "inst1":
$ asadmin start-instance --user admin --passwordfile pass.txt inst1
Timed out. Failed to start the server instance inst1. Please check the server log for more details.
CLI137 Command start-instance failed.
This is the error seen in the Admin GUI interface trying to start the same "inst1" instance:
Additional confirmation that the problem has been encountered can be gained from the instance's server.log output. First look for the start-up message:
May 5, 2010 5:22:24 PM com.sun.enterprise.admin.servermgmt.launch.ASLauncher buildCommand
... <start-up command truncated for clarity>
[#|2010-05-05T17:22:34.666+0200|INFO|sun-appserver2.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;Java HotSpot(TM) 64-Bit Server VM;1.6.0_11;Sun Microsystems Inc.;|CORE5076: Using [Java HotSpot(TM) 64-Bit Server VM, Version 1.6.0_11] from [Sun Microsystems Inc.]|#]
Then look for a stopping message further on the in the server.log file:
[#|2010-05-05T17:42:20.408+0200|INFO|sun-appserver2.1|javax.enterprise.system.container.web|_ThreadID=35;_ThreadName=RMI TCP Connection(1)-127.0.0.1;Sun GlassFish Enterprise Server v2.1 Patch02;|WEB0303: Stopping Sun GlassFish Enterprise Server v2.1 Patch02|#]
The timestamp from the ASLauncher build command is 5:22:24PM, so 17:22:24 converting to match the other timestamps. The timestamp from the stopping command is 17:42:20. As you can see, there is close to a 20 minute difference between these two values. The reason the time difference isn't precisely 20 minutes is that Java's java.util.Timer class does not guarantee real-time accuracy, so its possible that the timeout could trigger for values either just under 20 minutes, or just over.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms