AbstractHandleableCloseable.close hung thread in JBoss EAP 7.0
Issue
- We are seeing some threads hang in
org.jboss.remoting3.spi.AbstractHandleableCloseable.close
when JBoss EAP 7.0 is under heavy load.
default task-81" #7860 prio=5 os_prio=0 tid=0x00007f5a3c00b800 nid=0xa6be in Object.wait() [0x00007f5c549c9000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:190)
- locked <0x00000005fe53a948> (a java.lang.Object)
at org.jboss.naming.remote.client.HaRemoteNamingStore.close(HaRemoteNamingStore.java:403)
- locked <0x00000005fe612988> (a org.jboss.naming.remote.client.HaRemoteNamingStore)
at org.jboss.naming.remote.client.NamingStoreCache.release(NamingStoreCache.java:116)
- locked <0x00000005c5456130> (a org.jboss.naming.remote.client.NamingStoreCache)
at org.jboss.naming.remote.client.NamingStoreCache$1.close(NamingStoreCache.java:99)
at org.jboss.naming.remote.client.RemoteContext.close(RemoteContext.java:290)
at javax.naming.InitialContext.close(InitialContext.java:556)
at javax.naming.InitialContext.close(InitialContext.java:556)
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 7.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.