HTTPSession Replication Causes OC4J to Appear to Be Hung

(Doc ID 744080.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Containers for J2EE - Version to [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 02-May-2013***


When attempting to stress test an application deployed in a OAS cluster setup using HTTP session replication the following thread dump stack trace will appear. This causes the container to appear to have hung and must be restarted to continue using the application.

Thread dump 1/2 "AJPRequestHandler-RMICallHandler-14" prio=1 tid=0x08b380a0 nid=0x63c0 in
Object.wait() [0x62882000..0x62883020] at java.lang.Object.wait(Native Method) -
waiting on <0x7ba70148> (a
EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$ReaderLock) at
java.lang.Object.wait( at

EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$ReaderLock.acquire(WriterPreferenceRe - locked <
0x7ba70148> (a EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$ReaderLock)
at at at at at at
com.evermind.server.http.JGroupHttpSession.getValueFromMap( at
com.evermind.server.http.EvermindHttpSession.getAttribute( -
locked <
0x7ba6ff00> (a com.evermind.server.http.JGroupHttpSession) at
oracle.adf.share.http.HttpUtil.getAttribute( at


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