[jboss-jira] [JBoss JIRA] Closed: (JBREM-767) Avoid deadlock in callback BisocketClientInvoker when timeout == 0
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Fri Aug 31 21:59:18 EDT 2007
[ http://jira.jboss.com/jira/browse/JBREM-767?page=all ]
Ron Sigal closed JBREM-767.
---------------------------
Resolution: Done
Fixes for JBREM-765, JBREM-787, and having BisocketClientInvoker.handleDisconnect() wake up any threads waiting in BisocketClientInvoker.createSocket() have been applied to branch remoting_2_x.
The proposed fix "Another fix is for PingTimeTask to notify a thread waiting in createSocket() when an attempt to send a PING to the client fails." has not been implemented, since it adds a function for which PingTimerTask was not designed.
The unit test is passing on cruisecontrol.
> Avoid deadlock in callback BisocketClientInvoker when timeout == 0
> ------------------------------------------------------------------
>
> Key: JBREM-767
> URL: http://jira.jboss.com/jira/browse/JBREM-767
> Project: JBoss Remoting
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
> Reporter: Ron Sigal
> Assigned To: Ron Sigal
> Fix For: 2.2.2.GA, 2.4.0.Beta1 (Pinto)
>
>
> If timeout == 0 then org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket() can hang forever if the client side is unavailable.
> One fix is to not set timeout to 0, but currently the timeout value is inherited from the server invoker, for which timeout == 0 might be appropriate. One solution is to implement a separate timeout parameter for callback client invokers (JBREM-765).
> Another fix is for PingTimeTask to notify a thread waiting in createSocket() when an attempt to send a PING to the client fails.
--
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
More information about the jboss-jira
mailing list