Bug 793933 (JBEPP-1004) - Clustering not working with buddy replication enabled
Summary: Clustering not working with buddy replication enabled
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-1004
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal Packaging
Version: 5.2.0.DEV01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0.DEV02
Assignee: hfnukal@redhat.com
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-12 12:35 UTC by mposolda
Modified: 2011-09-22 06:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-10 08:45:54 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-1004 0 Major Closed Clustering not working with buddy replication enabled 2014-06-11 14:15:10 UTC

Description mposolda 2011-07-12 12:35:57 UTC
project_key: JBEPP

Clustering is not working when buddy replication is enabled. Cause of the error seems to be in bad packaging. JGroups and JBoss cache libraries should not be under server/all/deploy/gatein.ear/lib because they are already under server/all/lib .

To simulate issue, you can do this:

1) Enable buddy replication in $EPP_HOME/server/all/deploy/cluster/jboss-cache-manager.sar/META-INF/jboss-cache-manager-jboss-beans.xml for "standard-session-cache"

2) Start EPP 5.2 DEV01 with command:
./run.sh -c all

Now you will see error in server log :

07:47:32,491 WARN  [BuddyManager] Caught exception instantiating buddy locator
java.lang.RuntimeException: Unable to initialize AddressLocator
	at org.jboss.cache.buddyreplication.JGroups28AddressLocator.<init>(JGroups28AddressLocator.java:27)
	at org.jboss.cache.buddyreplication.NextMemberBuddyLocator.init(NextMemberBuddyLocator.java:92)
	at org.jboss.cache.buddyreplication.BuddyManager.createBuddyLocator(BuddyManager.java:224)
	at org.jboss.cache.buddyreplication.BuddyManager.setupInternals(BuddyManager.java:184)
	at org.jboss.cache.buddyreplication.BuddyManager.init(BuddyManager.java:272)
	...........
Caused by: java.lang.NoSuchFieldException: GET_PHYSICAL_ADDRESS
	at java.lang.Class.getField(Class.java:1520)
	at org.jboss.cache.buddyreplication.JGroups28AddressLocator.<init>(JGroups28AddressLocator.java:24)
	... 93 more


It's possible to fix this issue by deleting files from server/all/deploy/gatein.ear/lib :
jgroups-2.11.1-Final.jar
jgroups-2.6.13.GA.jar
jbosscache-core-3.2.7.GA.jar
hibernate-jbosscache2-3.3.2.GA.jar

Maybe also other libs should be deleted. For example, I am not sure about infinispan libs. AFAIK infinispan can be used with eXo JCR but we are still using JBoss cache with JCR, so infinispan is probably not required. And it's not part of EPP 5.1.1 .

Comment 2 Thomas Heute 2011-09-22 06:38:21 UTC
Release Notes Docs Status: Added: Not Required



Note You need to log in before you can comment on or make changes to this bug.