[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1144) Extend connection identity to server side

[Ron Sigal (JIRA)]

    [ https://issues.jboss.org/browse/JBREM-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577885#comment-12577885 ] 

Ron Sigal commented on JBREM-1144:
----------------------------------

The solution is to give each Lease a unique identity and to return that instead of the ServerInvoker's unique identity.

Testing:  added  testServerIdentityWithLeasingNewLease() to org.jboss.test.remoting.connection.identity.ServerIdentityTestCase to cover the situation when a lease changes and the ServerInvoker remains the same.

Waiting for results in hudson.


> Extend connection identity to server side
> -----------------------------------------
>
>                 Key: JBREM-1144
>                 URL: https://issues.jboss.org/browse/JBREM-1144
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.5.3.SP1, 2.2.3.SP3
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>             Fix For: 2.5.3.SP2, 2.2.3.SP4
>
>
> In JBREM-1128 "Introduce connection identity concept" and JBREM-1132 "CLONE [JBREM-1128] - Introduce connection identity concept", the server was equipped to recognized when a client had been replaced by another client.  In other words, clients were assigned an identity.  This concept should be extended to the server side, so that ConnectionValidator can detect that a server has been replaced.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira