My Oracle Support Banner

StackOverflowError During HTTP Session Failover With In-Memory Replication in Oracle GlassFish Server (Doc ID 1418953.1)

Last updated on OCTOBER 26, 2020

Applies to:

Oracle GlassFish Server - Version 2.1.1 and later
Information in this document applies to any platform.
Checked for relevance on 09/10/2013

Symptoms

When one instance of a running Oracle GlassFish Server cluster using in-memory replication is stopped and restarted, the following messages may be seen in the other instance's server.log file as the instance tries to form a cluster with the newly restarted instance:

[#|2011-11-04T07:57:24.193-0500|INFO|sun-appserver2.1.1|com.sun.enterprise.ee.web.sessmgmt.pipe|_ThreadID=[ID];_ThreadName=Executor - 3;|JxtaSenderPipeManager::pipePoolCount decremented = 6|#]

[#|2011-11-04T07:57:25.203-0500|INFO|sun-appserver2.1.1|com.sun.enterprise.ee.web.sessmgmt.pipe|_ThreadID=[ID];_ThreadName=Executor - 3;|JxtaSenderPipeManager::pipePoolCount decremented = 5|#]

[#|2011-11-04T07:57:26.214-0500|INFO|sun-appserver2.1.1|com.sun.enterprise.ee.web.sessmgmt.pipe|_ThreadID=[ID];_ThreadName=Executor - 3;|JxtaSenderPipeManager::pipePoolCount decremented = 4|#]

[#|2011-11-04T07:57:27.169-0500|INFO|sun-appserver2.1.1|ShoalLogger|_ThreadID=[ID];_ThreadName=ViewWindowThread:cluster1;|GMS View Change Received for group cluster1 : Members in view for JOINED_AND_READY_EVENT(before change analysis) are :
1: MemberId: xxx, MemberType: CORE, Address: xxx:uuid-xxxxxx
2: MemberId: xxx, MemberType: CORE, Address: xxx:uuid-xxxxxx
|#]

[#|2011-11-04T07:57:27.170-0500|INFO|sun-appserver2.1.1|ShoalLogger|_ThreadID=[ID];_ThreadName=ViewWindowThread:cluster1;JOINED_AND_READY_EVENT;pre0001m2;cluster1;|Analyzing new membership snapshot received as part of event : JOINED_AND_READY_EVENT for Member: xxxx of Group: cluster1|#]

[#|2011-11-04T07:57:27.170-0500|INFO|sun-appserver2.1.1|ShoalLogger|_ThreadID=[ID];_ThreadName=ViewWindowThread:cluster1;|Adding Joined And Ready member : pre0001m2 Group: :cluster1 StartupState:INSTANCE_STARTUP|#]

[#|2011-11-04T07:57:27.223-0500|INFO|sun-appserver2.1.1|com.sun.enterprise.ee.web.sessmgmt.pipe|_ThreadID=[[ID]];_ThreadName=Executor - 3;|JxtaSenderPipeManager::pipePoolCount decremented = 3|#]

[#|2011-11-04T07:57:28.233-0500|INFO|sun-appserver2.1.1|com.sun.enterprise.ee.web.sessmgmt.pipe|_ThreadID=[ID];_ThreadName=Executor - 3;|JxtaSenderPipeManager::pipePoolCount decremented = 2|#]

[#|2011-11-04T07:57:29.243-0500|INFO|sun-appserver2.1.1|com.sun.enterprise.ee.web.sessmgmt.pipe|_ThreadID=[ID];_ThreadName=Executor - 3;|JxtaSenderPipeManager::pipePoolCount decremented = 1|#]

[#|2011-11-04T07:57:30.253-0500|INFO|sun-appserver2.1.1|com.sun.enterprise.ee.web.sessmgmt.pipe|_ThreadID=[ID];_ThreadName=Executor - 3;|JxtaSenderPipeManager::pipePoolCount decremented = 0|#]

[#|2011-11-04T07:57:30.254-0500|WARNING|sun-appserver2.1.1|javax.enterprise.system.container.web|_ThreadID=[ID];_ThreadName=Executor - 3;_RequestID=<ReuestID>;|Out of pipes in JxtaReplicationSender pipepool. Disabling replication.|#]

[#|2011-11-04T07:57:30.256-0500|INFO|sun-appserver2.1.1|com.sun.enterprise.ee.web.sessmgmt.pipe|_ThreadID=[ID];_ThreadName=Executor - 3;|beginning attempt to reconnect|#]

[#|2011-11-04T07:57:36.281-0500|INFO|sun-appserver2.1.1|com.sun.enterprise.ee.web.sessmgmt.pipe|_ThreadID=[ID];_ThreadName=Executor - 3;|JxtaReplicationSender:Attempting to reconnect to pre0001m2|#]



followed by:

[#|2011-11-04T08:17:51.733-0500|WARNING|sun-appserver2.1.1|com.sun.enterprise.ee.web.sessmgmt.pipe|_ThreadID=[ID];_ThreadName=Executor - 3;_RequestID=<RequestID>;|doThreadedReconnect failed to reconnect
java.lang.StackOverflowError
at com.sun.enterprise.ee.web.sessmgmt.ReplicationHealthChecker.isStopping(ReplicationHealthChecker.java:1029)
at com.sun.enterprise.ee.web.sessmgmt.JoinNotificationEventHandler.checkAndDoJoinFor(JoinNotificationEventHandler.java:220)
at com.sun.enterprise.ee.web.sessmgmt.JoinNotificationEventHandler.checkAndDoJoinFor(JoinNotificationEventHandler.java:215)
at com.sun.enterprise.ee.web.sessmgmt.JoinNotificationEventHandler.doPollCheckForJoinProcessing(JoinNotificationEventHandler.java:303)
at com.sun.enterprise.ee.web.sessmgmt.JoinNotificationEventHandler.checkAndDoJoinFor(JoinNotificationEventHandler.java:252)
at com.sun.enterprise.ee.web.sessmgmt.JoinNotificationEventHandler.checkAndDoJoinFor(JoinNotificationEventHandler.java:215)
at com.sun.enterprise.ee.web.sessmgmt.JoinNotificationEventHandler.doPollCheckForJoinProcessing(JoinNotificationEventHandler.java:303)
      .....
      .....
      <Massive number of stack frames deleted as they repeat the same operations>
      .....
      .....
at com.sun.enterprise.ee.web.sessmgmt.JoinNotificationEventHandler.doPollCheckForJoinProcessing(JoinNotificationEventHandler.java:303)
at com.sun.enterprise.ee.web.sessmgmt.JoinNotificationEventHandler.checkAndDoJoinFor(JoinNotificationEventHandler.java:252)
at com.sun.enterprise.ee.web.sessmgmt.JoinNotificationEventHandler.checkAndDoJoinFor(JoinNotificationEventHandler.java:215)
at com.sun.enterprise.ee.web.sessmgmt.JoinNotificationEventHandler.doPollCheckForJoinProcessing(JoinNotificationEventHandler.java:303)
|#]

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!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.