Remote Naming thread holding lock causing thread pile up when closing in JBoss EAP 6.4

Environment

Red Hat JBoss Enterprise Application Platform (EAP) 6.4

Issue

• Our application is using remote naming to post JMS messages, when under heavy load with a lot of clients opening & closing remote naming connections, we found a lot of threads blocked such as :

   java.lang.Thread.State: BLOCKED
	at org.jboss.naming.remote.client.EndpointCache.get(EndpointCache.java:41)
	- waiting to lock <1c3bfa61> (a org.jboss.naming.remote.client.EndpointCache) owned by "Thread-1 (HornetQ-client-global-threads-2114338462)"

Resolution

Apply JBoss EAP 6.4 Cumulative Patch (CP) 6

Root Cause

This content is not included.BZ-1278606 - Remote Naming holding cache lock while closing leading to thread pile up

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.