JVM hangs after deadlock between JBoss Remoting and xalan

Solution Unverified - Updated -

Issue

  • JVM hangs after deadlock between JBoss Remoting and xalan :
Found one Java-level deadlock:
=============================
"ajp-10.220.35.49-8009-292":
  waiting to lock monitor 0x00002aae383fdf88 (object 0x00002aab02e67688, a org.jboss.web.tomcat.service.WebCtxLoader$ENCLoader),
  which is held by "ajp-10.220.35.49-8009-32"
"ajp-10.220.35.49-8009-32":
  waiting to lock monitor 0x00002aae3d0ad3c8 (object 0x00002aaaf1a5cd88, a org.jboss.bootstrap.NoAnnotationURLClassLoader),
  which is held by "WorkManager(2)-52"
"WorkManager(2)-52":
  waiting to lock monitor 0x00002aadf83ff2c0 (object 0x00002aaaf1a08278, a sun.misc.Launcher$AppClassLoader),
  which is held by "ajp-10.220.35.49-8009-32"

Environment

  • JBoss Enterprise Application Platform (EAP)

    • 5.1.0
  • Oracle JDK

    • 1.6.0_18-b07

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