[jboss-remoting-issues] [JBoss JIRA] Updated: (JBREM-1238) Need invocation timeouts in synchronized blocks in MicroRemoteClientInvoker that create and terminate leases

[Ron Sigal (JIRA)]

     [ https://jira.jboss.org/browse/JBREM-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Sigal updated JBREM-1238:
-----------------------------

        Fix Version/s: 2.2.3.SP3
    Affects Version/s: 2.2.3.SP2


> Need invocation timeouts in synchronized blocks in MicroRemoteClientInvoker that create and terminate leases 
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBREM-1238
>                 URL: https://jira.jboss.org/browse/JBREM-1238
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.3.SP2, 2.5.3.SP1
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>             Fix For: 2.2.3.SP3, 2.5.3.SP2
>
>
> org.jboss.remoting.MicroRemoteClientInvoker.establishLease() and MicroRemoteClientInvoker.terminateLease() do network invocations inside synchronized blocks, and, if the invocations get hung up, then it becomes impossible to create new connections with leasing enabled.  Setting the 'timeout" parameter appropriately would work around the problem, but some users, notably JBossMessaging, set "timeout" to 0.
> A speclal case timeout parameter should be used, along with the per invocation timeout facility, to prevent MicroRemoteClientInvoker from getting stuck in establishLease() or terminateLease().

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira