[jboss-jira] [JBoss JIRA] Closed: (JBREM-722) BisocketClientInvoker should start pinging on control connection without waiting for call to createsocket()

[Ron Sigal (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBREM-722?page=all ]

Ron Sigal closed JBREM-722.
---------------------------

    Resolution: Done

Bisocket unit tests pass on cruisecontrol.

> BisocketClientInvoker should start pinging on control connection without waiting for call to createsocket()
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBREM-722
>                 URL: http://jira.jboss.com/jira/browse/JBREM-722
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions:  2.2.0.Beta1 (Bluto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.0.Beta2 (Bluto)
>
>
> Currently, a callback BisocketClientInvoker waits for the first call to createSocket() to start pinging on control connection.  But the BisocketServerInvoker.ControlMonitorTimerTask on the client side doesn't start testing for pings until it gets the first ping.  So, if the control connection were to break before the first call to createSocket(), the ControlMonitorTimerTask wouldn't recreate the control connection and createSocket() wouldn't be able to get a new socket.

-- 
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