[jboss-jira] [JBoss JIRA] Updated: (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=all ]

Ron Sigal updated JBREM-779:
----------------------------

    Fix Version/s: 2.2.2.GA
                       (was: 2.2.1.SP1)

Fixed in Remoting 2.2.2.GA rather than 2.2.1.SP1.

> 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.4.0.Beta1 (Pinto), 2.2.1.GA, 2.2.0.SP4_CP02
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.0.SP4_CP02, 2.2.2.GA
>
>
> 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