Bug 1012850 - RemoteDomainConnection.close() will block forever if the master HC is not running
Summary: RemoteDomainConnection.close() will block forever if the master HC is not run...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER4
: EAP 6.2.0
Assignee: Ivo Studensky
QA Contact: Petr Kremensky
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks: 1045634
TreeView+ depends on / blocked
 
Reported: 2013-09-27 09:18 UTC by Ivo Studensky
Modified: 2018-12-06 15:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:20:22 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-1511 0 Major Closed RemoteDomainConnection.close() will block forever if the master HC is not running 2018-07-19 10:29:04 UTC

Description Ivo Studensky 2013-09-27 09:18:51 UTC
Description of problem:
RemoteDomainConnection.close() overrides FutureManagementChannel.close() to first send a "unregister" message to the master HC before calling the superclass functionality.

Problem is this call tries to open a connection to the master and will block forever waiting for it to connect if the master isn't available, as seen at http://fpaste.org/18232/37105700/

That example was from AutoIgnoredResourcesDomainTestCase which is concurrently shutting down the hosts in the domain, meaning the master can be shutting down in the middle of or prior to slave shutdown.


A backport of WFLY-1511 to EAP 6.2.

Comment 1 Ivo Studensky 2013-09-27 11:48:59 UTC
Relevant PR:

https://github.com/jbossas/jboss-eap/pull/476

Comment 5 Petr Kremensky 2013-10-09 11:17:03 UTC
Verified on EAP 6.2.0.ER5.


Note You need to log in before you can comment on or make changes to this bug.