[jbosscache-issues] [JBoss JIRA] Assigned: (JBCACHE-1517) Possibility of upgrading to JGroups 2.8 ?

[Galder Zamarreno (JIRA)]

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

Galder Zamarreno reassigned JBCACHE-1517:
-----------------------------------------

    Assignee: Galder Zamarreno  (was: Manik Surtani)


> Possibility of upgrading to JGroups 2.8 ?
> -----------------------------------------
>
>                 Key: JBCACHE-1517
>                 URL: https://jira.jboss.org/jira/browse/JBCACHE-1517
>             Project: JBoss Cache
>          Issue Type: Thirdparty Change
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 3.2.0.GA
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>
> Can we upgrade JBC 3.2 to use JGroups 2.8? Bela said JGroups 2.6 and 2.8 don't have on the wire 
> compatibility, so if JBC 3.2 and JBC 3.1 clusters would not be able to cluster.
> org.jboss.cache.buddyreplication.NextMemberBuddyLocator is using IpAddress to figure out if candidate 
> and data owner are in the same machine:
>       // assume they're both IpAddresses??
>       InetAddress inetC = ((IpAddress) candidate).getIpAddress();
>       InetAddress inetD = ((IpAddress) dataOwner).getIpAddress();
> There's also some test classes making use of IpAddress, i.e. CacheJmxWrapperTest and GlobalTransactionTest

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