[jboss-jira] [JBoss JIRA] Commented: (JBREM-875) CLONE -Have ServerInvokerCallbackHandler register as connection listener [JBREM-873]

[Ron Sigal (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-875?page=comments#action_12393208 ] 
            
Ron Sigal commented on JBREM-875:
---------------------------------

Unit tests:

org.jboss.test.remoting.transport.bisocket.connectionfailure.BisocketCallbackConnectionFailureTestCase
org.jboss.test.remoting.transport.http.connectionfailureHttpCallbackConnectionFailureTestCase
org.jboss.test.remoting.transport.rmi.connectionfailure.RMICallbackConnectionFailureTestCase
org.jboss.test.remoting.transport.socket.connectionfailure.SocketCallbackConnectionFailureTestCase

> CLONE -Have ServerInvokerCallbackHandler register as connection listener [JBREM-873]
> ------------------------------------------------------------------------------------
>
>                 Key: JBREM-875
>                 URL: http://jira.jboss.com/jira/browse/JBREM-875
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.0.SP2
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> This feature is implemented in response to JBPAPP-402 :"In certain situations createQueueConnection can hang".  
> JBossMessaging does not, in general, call org.jboss.remoting.callback.ServerInvokerCallbackHandler.destroy() when a lease indicates that a connection has failed.  More generally, the need to call ServerCallbackHandler.destroy() is not documented in the Remoting Guide, so it is possible that JBossMessaging is not alone.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira