[jboss-jira] [JBoss JIRA] Closed: (JBREM-765) Add a separate timeout parameter for callback clients

[Ron Sigal (JIRA)]

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

Ron Sigal closed JBREM-765.
---------------------------

    Resolution: Done

The provision of a unit test for the RMI transport will be done under JBREM-799 "Add a separate timeout parameter for callback clients, part 2".

> Add a separate timeout parameter for callback clients
> -----------------------------------------------------
>
>                 Key: JBREM-765
>                 URL: http://jira.jboss.com/jira/browse/JBREM-765
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      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)
>
>
> Currently, the timeout set for the server filters down to callback client invokers.  However, it would be useful to be able to specify a different timeout value for callback clients.
> Example.  In JBossMessaging the server timeout is set to 0.  This causes a problem for bisocket callback client invokers, since they create sockets by sending a message to the client side and then calling wait().  If timeout == 0 and the client dies, then the thread in wait() could wait forever.

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