JBoss Deadlock in org.jboss.util.NestedThrowable
Environment
- JBoss Application Platform (EAP)
- 4.2
- 4.3
Issue
- JBoss becomes unresponsive. Checking thread dumps, it looks like there could be a deadlock as multiple threads are stalled up in the initialization of org.jboss.util.NestedThrowable or its Utils subclass:
3XMTHREADINFO "ajp-localhost-8009-34" J9VMThread:0x0000000117AB1B00, j9thread_t:0x00000001179FEA60, java/lang/Thread:0x070000006F4F59D8, state:CW, prio=5
3XMTHREADINFO1 (native thread ID:0x1350AB, native priority:0x5, native policy:UNKNOWN)
3XMTHREADINFO3 Java callstack:
4XESTACKTRACE at java/lang/Object.wait(Native Method)
4XESTACKTRACE at java/lang/Object.wait(Object.java:167(Compiled Code))
4XESTACKTRACE at java/lang/J9VMInternals.initialize(J9VMInternals.java:130(Compiled Code))
4XESTACKTRACE at java/lang/Class.forNameImpl(Native Method)
4XESTACKTRACE at java/lang/Class.forName(Class.java:136(Compiled Code))
4XESTACKTRACE at org/jboss/util/NestedThrowable$1.class$(NestedThrowable.java:113)
4XESTACKTRACE at org/jboss/util/NestedThrowable$Util.<clinit>(NestedThrowable.java:113)
...
3XMTHREADINFO "ajp-localhost-8009-33" J9VMThread:0x0000000116BC1C00, j9thread_t:0x0000000116A430A0, java/lang/Thread:0x070000000059BE08, state:CW, prio=5
3XMTHREADINFO1 (native thread ID:0x438099, native priority:0x5, native policy:UNKNOWN)
3XMTHREADINFO3 Java callstack:
4XESTACKTRACE at java/lang/Object.wait(Native Method)
4XESTACKTRACE at java/lang/Object.wait(Object.java:167(Compiled Code))
4XESTACKTRACE at java/lang/J9VMInternals.initialize(J9VMInternals.java:130(Compiled Code))
4XESTACKTRACE at org/jboss/util/NestedThrowable.<clinit>(NestedThrowable.java:51)
...
Resolution
- This content is not included.One-Off Fix for JBoss EAP 4.2.0.GA_CP04
- Content from jira.jboss.org is not included.Upgrade to EAP 4.2.0.GA_CP08 or later or 4.3.0.GA_CP07 or later
Root Cause
- Content from jira.jboss.org is not included.Content from jira.jboss.org is not included.https://jira.jboss.org/jira/browse/JBCOMMON-35
Diagnostic Steps
- Troubleshoot using thread dumps and additional steps mentioned in Java application unresponsive
Components
Category
Tags
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.