JBoss thread contention on org.jboss.jca.core.tracer.Tracer

Solution Verified - Updated -

Issue

  • We are facing performance concerns with thread contention on org.jboss.jca.core.tracer.Tracer like below:
"default-threads - 22" #400 prio=5 os_prio=0 tid=0x000055e2aa223000 nid=0xa9139 waiting for monitor entry [0x00007f3e9fa06000]
   java.lang.Thread.State: BLOCKED (on object monitor)
    at org.jboss.jca.core.tracer.Tracer.pushCCMContext(Tracer.java:586)
    - waiting to lock <0x00000005c27e67d0> (a java.lang.Class for org.jboss.jca.core.tracer.Tracer)
    at org.jboss.jca.core.connectionmanager.ccm.CachedConnectionManagerImpl.pushMetaAwareObject(CachedConnectionManagerImpl.java:438)
    at org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.setup(CachedConnectionManagerSetupProcessor.java:104)
    at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:52)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

Environment

  • JBoss Enterprise Application Platform (EAP) 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content