[jboss-jira] [JBoss JIRA] (JBMESSAGING-1921) Using separate thread to stop a sucker so that the failover thread won't get blocked

Yong Hao Gao (JIRA) jira-events at lists.jboss.org
Wed Apr 18 04:22:20 EDT 2012


Yong Hao Gao created JBMESSAGING-1921:
-----------------------------------------

             Summary: Using separate thread to stop a sucker so that the failover thread won't get blocked
                 Key: JBMESSAGING-1921
                 URL: https://issues.jboss.org/browse/JBMESSAGING-1921
             Project: JBoss Messaging
          Issue Type: Enhancement
    Affects Versions: 1.4.8.SP7, 1.4.0.SP3.CP14
            Reporter: Yong Hao Gao
            Assignee: Yong Hao Gao
             Fix For: 1.4.0.SP3.CP15, 1.4.8.SP8


The failover thread calls MessageSucker.stop() during removal of suckers for the failed node. The stop() method will always attempt to make some remoting calls regardless of the connection condition (which may have already been broken). On some network failure conditions the stop() can take significant time to finish, thus make the failover thread block and the whole failover process takes a long time to complete. 

Using a separate thread to do the closing can improve the failover time in such cases.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list