[jbosscache-issues] [JBoss JIRA] Commented: (JBCACHE-1517) Possibility of upgrading to JGroups 2.8 ?
[
https://jira.jboss.org/jira/browse/JBCACHE-1517?page=com.atlassian.jira.p...
]
Bela Ban commented on JBCACHE-1517:
-----------------------------------
The way to get the physical address in JGroups 2.8 is to send a GET_PHYSICAL_ADDRESS event
down:
Address logical_addr; // logical address
PhysicalAddress physical_addr; // physical address (interface)
physical_addr=(PhysicalAddress)channel.downcall(Event.GET_PHYSICAL_ADDRESS,
logical_addr);
if (physical_addr instanceof IpAddress) {
IpAddress addr=(IpAddress)physical_addr;
// use addr (getInetAddress(), getPort())
}
else
// error
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: Manik Surtani
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