Bug 1278606 - [GSS](6.4.z) Remote Naming holding cache lock while closing leading to thread pile up
Summary: [GSS](6.4.z) Remote Naming holding cache lock while closing leading to thread...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Naming
Version: 6.4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.6
Assignee: Dmitrii Tikhomirov
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1235746 1280507 1280510 1297478
TreeView+ depends on / blocked
 
Reported: 2015-11-05 23:46 UTC by Brad Maxwell
Modified: 2019-09-12 09:14 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-17 11:46:25 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-12544 0 Major Verified [GSS](7.0.z) Remote Naming holding cache lock while closing leading to thread pile up 2017-11-09 04:07:25 UTC
Red Hat Knowledge Base (Solution) 2135131 0 None None None 2016-01-21 23:46:18 UTC

Description Brad Maxwell 2015-11-05 23:46:41 UTC 
Remote Naming holding cache lock while closing leading to thread pile up

   java.lang.Thread.State: BLOCKED
	at org.jboss.naming.remote.client.EndpointCache.get(EndpointCache.java:41)
	- waiting to lock <2b3bce62> (a org.jboss.naming.remote.client.EndpointCache) owned by "Thread-2 (HornetQ-client-global-threads-1312378312)"
Comment 2 Enrique Gonzalez Martinez 2015-11-06 07:46:05 UTC 
Hi brad, I think it would be really helpful if you provide the whole stack.
Comment 9 Jan Martiska 2016-01-20 12:01:16 UTC 
Verified in EAP 6.4.6.CR2
Comment 10 Petr Penicka 2017-01-17 11:46:25 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.
Comment 11 Petr Penicka 2017-01-17 11:47:45 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.
Note You need to log in before you can comment on or make changes to this bug.