My Oracle Support Banner

Glassfish Server Instance Startup Times Out After 20 Minutes. (Doc ID 1136123.1)

Last updated on APRIL 20, 2020

Applies to:

Oracle GlassFish Server - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

When an already running Node Agent starts up an instance, the start-up sequence of an application server instance is subject to an internal timeout, which by default is set to 20 minutes.  If the start-up sequence takes longer than this timeout then the instance is terminated. 

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":


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.

Changes

 

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.