The Glassfish Server Node Agent Aborts Instances That Take Too Long to Startup or Shutdown (Doc ID 1267667.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle GlassFish Server - Version 9.1 and later
Information in this document applies to any platform.
***Checked for relevance on 30-Sep-2013***

Symptoms

Instance Startup Symptoms

Instances that are automatically started by the node agent, and which take more than ten minutes to complete their startup, are terminated by the node agent.

Note that this article does not cover the situation where an already running Node Agent starts an instance and times it out after twenty minutes, please refer to <Note:1136123.1> for details of that use case.

In the node agent log file the following messages are seen:

[#|2010-11-15T17:03:37.720+0000|WARNING|sun-appserver2.1.1|javax.ee.enterprise.system.tools.admin|_ThreadID=11;_ThreadName=main;|Thread Thread-22 for task com.sun.enterprise.ee.nodeagent.NodeAgent$StopServerTask@127890 has timed out after 120000 ms and is still a live.|#]

[#|2010-11-15T17:03:37.726+0000|WARNING|sun-appserver2.1.1|javax.ee.enterprise.system.tools.admin|_ThreadID=11;_ThreadName=main;|Thread Thread-22 for task com.sun.enterprise.ee.nodeagent.NodeAgent$StopServerTask@127890 did not respond to the interrupt.|#]


The instance log will contain normal messages as part of its startup, for example you would see the initial message at the beginning of the startup sequence:

[#|2010-11-15T16:39:49.389+0000|INFO|sun-appserver2.1.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Starting Sun GlassFish Enterprise Server v2.1.1 Patch08 ((v2.1 Patch14)(9.1_02 Patch20)) (build b01-p08) ...|#]


Followed by a sequence of other log messages, eventually leading to a shutdown notification:

[#|2010-11-15T16:49:48.142+0000|INFO|sun-appserver2.1.1|javax.enterprise.system.container.web|_ThreadID=17;_ThreadName=RMI TCP Connection(1)-127.0.0.1;Sun GlassFish Enterprise Server v2.1.1 Patch08;|WEB0303: Stopping Sun GlassFish Enterprise Server v2.1.1 Patch08|#]


If you look at the timestamps in the two messages above, which are 16:39:49 and 16:49:48, there is an approximately 10 minute period between them.

Instance Shutdown Symptoms

Likewise, when the node agent is shutdown, it terminates any running instances.  With instance termination, the default timeout is two minutes.  A similar message is seen in the node agent when an instance exceeds the timeout:

[#|2010-11-15T17:03:37.720+0000|WARNING|sun-appserver2.1.1|javax.ee.enterprise.system.tools.admin|_ThreadID=11;_ThreadName=main;|Thread Thread-22 for task com.sun.enterprise.ee.nodeagent.NodeAgent$StopServerTask@127890 has timed out after 120000 ms and is still a live.|#]

[#|2010-11-15T17:03:37.726+0000|WARNING|sun-appserver2.1.1|javax.ee.enterprise.system.tools.admin|_ThreadID=11;_ThreadName=main;|Thread Thread-22 for task com.sun.enterprise.ee.nodeagent.NodeAgent$StopServerTask@127890 did not respond to the interrupt.|#]


While terminating an instance during shutdown might not initially sound like an issue, if the applications are performing some processing as part of the termination, interrupting that processing might not be desired.

Changes

This problem could be encountered by the deployment of a new or updated application that increases the overall initialization time over 10 minutes, or problems with applications that communicate with enterprise information systems, as part of their initialization, that are performing poorly and increasing the time an application takes to initialize.

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