[jboss-jira] [JBoss JIRA] Updated: (JBAS-7254) Remove ChannelFactory additional_data usage

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated JBAS-7254:
-----------------------------------

    Fix Version/s: JBossAS-5.2.0.Beta1
         Assignee: Vladimir Blagojevic  (was: Brian Stansberry)


> Remove ChannelFactory additional_data usage
> -------------------------------------------
>
>                 Key: JBAS-7254
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7254
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>            Assignee: Vladimir Blagojevic
>             Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1
>
>
> org.jboss.ha.framework.server.JChannelFactory supports a form of logical addresses by setting additional_data on the channel (see setChannelUniqueId()).  This should be replaced by calling the JGroups 2.8 Channel.setName() method.
> The ClusterPartition.verifyNodeIsUnique() method uses the additional_data to try to ensure that the same node cannot rejoin the group until its previous incarnation has been removed from the view. Confirm that JGroups 2.8 handles this itself, removing the need for the AS to do it. Then make verifyNodeIsUnique a deprecated no-op (if this JIRA is done for AS 5.2) and remove it for AS 6.  Can't just remove the method in 5.2 as it is protected; some subclass somewhere may invoke or override it.

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