Weblogic Server Causing Deadlock While Calling Webservices In C2M (Doc ID 2752446.1)

Last updated on JUNE 02, 2024

Applies to:

Symptoms

On : 2.7.0.1.0 version, Cross-Product Maintenance

weblogic server causing deadlock while calling webservices in C2M

Having issues with webservice calls within integration cluster . Two Servers in integration cluster(4 node cluster) goes to failed state due to deadlock on weblogic and which is causing the stuckthreads and DB connections exceed.
 
Thread '[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Default (self-tuning)'' is waiting to acquire lock 'groovy.lang.GroovyClassLoader$InnerLoader@2f5e5d07' that is held by thread '[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)''

Stack trace:
------------
java.lang.Class.getDeclaredMethods0(Native Method)
java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
java.lang.Class.getDeclaredMethods(Class.java:1975)
org.codehaus.groovy.vmplugin.v5.Java5.configureClassNode(Java5.java:362)
org.codehaus.groovy.ast.ClassNode.lazyClassInit(ClassNode.java:265)
org.codehaus.groovy.ast.ClassNode.getUnresolvedSuperClass(ClassNode.java:1004)
org.codehaus.groovy.ast.ClassNode.getUnresolvedSuperClass(ClassNode.java:999)
org.codehaus.groovy.transform.stc.StaticTypeCheckingVisitor.extractGenericsConnectionsForSuperClassAndInterfaces(StaticTypeCheckingVisitor.java:4278)

Changes

Cause

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