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

[Ron Sigal (JIRA)]

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

When org.jboss.remoting.ServerInvoker creates an org.jboss.remoting.callback.ServerInvokerCallbackHandler, it will optionally register the ServerInvokerCallbackHandler as an org.jboss.remoting.ConnectionListener with its org.jboss.remoting.ConnectionNotifier.  Then, if leasing is enabled and the lease associated with callback connection fails, the ServerInvokerCallbackHandler.handleConnectionException() will be called and it will call ServerInvokerCallbackHandler.destroy(), which will close the callback org.jboss.remoting.Client (if one exists).

The behavior may be configured by setting the configuration parameter ServerInvoker.REGISTER_CALLBACK_LISTENER (actual value "registerCallbackListener") to "true" or "false".

The default behavior is to register the ServerInvokerCallbackHandler. 

> Have ServerInvokerCallbackHandler register as connection listener
> -----------------------------------------------------------------
>
>                 Key: JBREM-873
>                 URL: http://jira.jboss.com/jira/browse/JBREM-873
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP2
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.SP4
>
>
> 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