[jboss-remoting-issues] [JBoss JIRA] Closed: (JBREM-1160) CLONE [JBREM-1159] - Version compatibility problem with leasing

[Ron Sigal (JIRA)]

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

Ron Sigal closed JBREM-1160.
----------------------------

    Resolution: Done


Updated test in ServerInvoker to test for leasePingerID == null, and updated org.jboss.test.remoting.versioning.lease.LeaseVersionTestCase by putting "useClientConnectionIdentity=true" in InvokerLocator.

LeaseVersionTestCase passes in the version compatibility test suite. 

> CLONE [JBREM-1159] - Version compatibility problem with leasing
> ---------------------------------------------------------------
>
>                 Key: JBREM-1160
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1160
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.3.SP1
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>             Fix For: 2.2.3.SP2
>
>         Attachments: jboss-remoting.jar
>
>
> If "useClientConnectionIdentity" is set to "true, then org.jboss.remoting.ServerInvoker.updateClientLease() tries to get a leasePingerId from the request map and compare it to the leasePingerId in a Lease.  But if the InvocationRequest came from an older client that doesn't know about connection identity, the value of leasePingerId is null.  The test calls 
>   leasePingerId.equals(clientLease.getLeasePingerId()
> which causes a NullPointerException.  The test should be reversed.  Also, org.jboss.test.remoting.versioning.lease.LeaseVersionTestCase should be strengthened to catch this problem.

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