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

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.

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

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

Cause

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