Performance Degradation due to Locks on Oracle.J2ee.Connector.Proxy.Bcelproxyclassloader class in Oracle Application Server 10.1.3.5 (Doc ID 1385494.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Containers for J2EE - Version: 10.1.3.5.0 and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.

Symptoms

An application has been deployed into 10.1.3.5 OC4J .
And application performance degrades due to some locks and waits on the following class: oracle.j2ee.connector.proxy.BCELProxyClassLoader

Taking a java thread dump of the OC4J,  many threads are waiting on an instance of oracle.j2ee.connector.proxy.BCELProxyClassLoader class
as the following :

"RMICallHandler-372" prio=10 tid=0x180f8400 nid=0x2051 waiting for monitor entry [0x19c50000]
java.lang.Thread.State: BLOCKED (on object monitor)
at oracle.oc4j.sql.proxy.ConstructionKey.createConstructionKey(ConstructionKey.java:375)
- waiting to lock <0x34e4fc98> (a oracle.j2ee.connector.proxy.BCELProxyClassLoader)
at oracle.oc4j.sql.proxy.SQLBCELProxy.oc4j_createConstructionKey(SQLBCELProxy.java:385)
...

at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:497)
at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:415)oxy.BCELProxyClassLoader

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