[jboss-jira] [JBoss JIRA] Closed: (JBREM-726) BisocketServerInvoker control connection creation needs to be in loop

[Ron Sigal (JIRA)]

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

Ron Sigal closed JBREM-726.
---------------------------

    Resolution: Done

There is a new configuration parameter, org.jboss.remoting.transport.bisocket.Bisocket.MAX_RETRIES (actual value "maxRetries") that is used by BisocketClientInvoker to govern the number of attempts to get the secondary locator, and in BisocketServerInvoker to govern the number of attempts to create both ordinary and control sockets. The default value is 10.

> BisocketServerInvoker control connection creation needs to be in loop
> ---------------------------------------------------------------------
>
>                 Key: JBREM-726
>                 URL: http://jira.jboss.com/jira/browse/JBREM-726
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions:  2.2.0.Beta1 (Bluto)
>            Reporter: Tim Fox
>         Assigned To: Ron Sigal
>             Fix For: 2.2.0.Beta2 (Bluto)
>
>
> When using the bisocket transport the creation of non control tcp connections is done in a retry to loop to prevent failures which may happen when trying to create connections in Windows (known windowx bug).
> However creation of the tcp connection to be used for the bisocket control connection does not appear to be protected in the same way. This can cause JBM intermittent test failures when running on Windows.

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