JBoss deadlocks and hangs accessing synchronized Seam components

Solution Verified - Updated -

Issue

  • JBoss hangs due to threads that are deadlocked on synchronized Seam components, like so:
    "ajp-0.0.0.0-8009-1" daemon prio=10 tid=0x000000004b8c4800 nid=0x350c waiting on condition [0x0000000061778000]
   java.lang.Thread.State: TIMED_WAITING (parking)
     at sun.misc.Unsafe.park(Native Method)
     - parking to wait for  <0x0000000774430a88> (a java.util.concurrent.locks.ReentrantLock$FairSync)
     at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:198)
     at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireNanos(AbstractQueuedSynchronizer.java:905)
     at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireNanos(AbstractQueuedSynchronizer.java:1224)
     at java.util.concurrent.locks.ReentrantLock.tryLock(ReentrantLock.java:416)
     at org.jboss.seam.core.SynchronizationInterceptor.aroundInvoke(SynchronizationInterceptor.java:28)
     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
     at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
     at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:185)
     at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:103)

Environment

  • JBoss Enterprise Application Platform (EAP)
    • Seam

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.