[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1561) ConnectionFactoryCallbackHandler$CallbackConnectionListener should call disconnectTimeout(0) in connection failure handling
Howard Gao (JIRA)
jira-events at lists.jboss.org
Thu Jul 30 06:03:29 EDT 2009
[ https://jira.jboss.org/jira/browse/JBMESSAGING-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard Gao closed JBMESSAGING-1561.
-----------------------------------
Resolution: Done
In ClientClusteredConnectionFactoryDelegate.closeCallback() a boolean parameter is added to the method to indicate the reason for closing the callback. If this parameter is passed true, it calls remoting.setFailed() rather than stop().
> ConnectionFactoryCallbackHandler$CallbackConnectionListener should call disconnectTimeout(0) in connection failure handling
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBMESSAGING-1561
> URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1561
> Project: JBoss Messaging
> Issue Type: Bug
> Affects Versions: 1.4.0.SP3.CP07, 1.4.2.GA.SP1
> Reporter: Howard Gao
> Assignee: Howard Gao
> Priority: Minor
> Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
>
>
> In ConnectionFactoryCallbackHandler$CallbackConnectionListener, the failure handling will close/stop the old remoting client and create/start a new one. The close/stop will call Client.disconnect() in the end. It should be called the Client.setDisconnectTimeout(0) before the disconnect call, so that the client will not attempt to do any remote calls in the closing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list