[jboss-jira] [JBoss JIRA] Commented: (JBREM-663) Put org.jboss.remoting.LeasePinger on separate thread.

[Ron Sigal (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-663?page=comments#action_12350766 ] 
            
Ron Sigal commented on JBREM-663:
---------------------------------

Yes, it is checked in on the 2.x branch.

-Ron
===================



> Put org.jboss.remoting.LeasePinger on separate thread.
> ------------------------------------------------------
>
>                 Key: JBREM-663
>                 URL: http://jira.jboss.com/jira/browse/JBREM-663
>             Project: JBoss Remoting
>          Issue Type: Task
>      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.Beta1 (Bluto)
>
>
> It has been observed in running JBossMessaging test suite that sometimes org.jboss.remoting.LeasePinger and org.jboss.remoting.ConnectionValidator, which both use the single java.util.Timer in org.jboss.remoting.util.TimerUtil, can get in each others way.  In particular, LeasePinger got hung up trying to ping a dead server and held up the ConnectionValidator until it timed out.

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