OC4J With A Web Application Involving OID Access Hangs Sporadically (Doc ID 1306180.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Containers for J2EE - Version 10.1.2.2.0 to 10.1.2.2.0 [Release AS10gR2]
Information in this document applies to any platform.
***Checked for relevance on 11-January-2013***

Symptoms

In AS 10.1.2.2, a web application involving OID access sporadically hangs which requires a restart of the container.


Thread dump were generated. It appears that this thread is the problem since
it is appearing many times waiting to lock a ldap resource:



"AJPRequestHandler-ApplicationServerThread-10" prio=5 tid=0x00dd6868
nid=0x59 waiting for monitor
entry [0x83f0f000..0x83f0fc28]
at oracle.security.jazn.spi.ldap.DirContextPool.acquireContext(Unknown Source)
- waiting to lock <0xadfa2018> (a oracle.security.jazn.spi.ldap.DirContextPool)
at oracle.security.jazn.spi.ldap.ExtRealm.getUser(Unknown Source)
at oracle.security.jazn.oc4j.RealmUserManager.getUser(UnknownSource)
at oracle.security.jazn.oc4j.FilterUserManager.getUser(UnknownSource)
at com.evermind.server.http.AJPRequestHandler.loadRemoteUser(AJPRequestHandler.java:429)
at com.evermind.server.http.AJPRequestHandler.initRequest(AJPRequestHandler.java:483)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:194)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)

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