[jboss-jira] [JBoss JIRA] Commented: (JBREM-779) BisocketClientInvoker should guard agains scheduling on an expired Timer, part 2

[Ron Sigal (JIRA)]

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

The fix has been applied to branch remoting_2_2_0_SP4_CP. It should also be applied to remoting_2_2_0_GA and remoting_2_x.

Unit test:  several test methods have been added to org.jboss.test.remoting.transport.bisocket.TimerReuseTestCase.

> BisocketClientInvoker should guard agains scheduling on an expired Timer, part 2
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-779
>                 URL: http://jira.jboss.com/jira/browse/JBREM-779
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.0.SP4, 2.2.1.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.0.SP4_CP02, 2.2.1.SP1
>
>
> The fix for JBREM-748 "BisocketClientInvoker should guard agains scheduling on an expired Timer" involved two places in BisocketClientInvoker where the Timer is created:  the constructor and replaceControlSocket().  The fix in replaceControlSocket(), however, while applied to the remoting_2_x branch, was omitted on the remoting_2_2_0_SP4_CP and remoting_2_2_GA branches.  It should be applied on those latter two branches.

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