Bug 793707 (JBEPP-782)

Summary: Cluster communication in default configuration
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: Martin Weiler <mweiler>
Component: PortalAssignee: hfnukal <hfnukal>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0.GACC: christoph.hennes, epp-bugs, mweiler
Target Milestone: ---   
Target Release: 5.1.1.DEV01   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-782
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Two instances of EPP 5.1 in default configuration on the same network
Last Closed: 2011-04-19 12:11:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Martin Weiler 2011-01-27 14:11:19 UTC 
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000006Ga8a
project_key: JBEPP

We see clustering communication between two EPP 5.1 instances, although they are started in the 'default' configuration:

15:06:31,240 INFO  [STDOUT] 
---------------------------------------------------------
GMS: address is 127.0.0.1:37378 (cluster=udp)
---------------------------------------------------------
15:06:33,339 INFO  [RPCManagerImpl] Received new cluster view: [127.0.0.1:37378|0] [127.0.0.1:37378]

and then, when the second server starts up:
15:07:54,653 INFO  [RPCManagerImpl] Received new cluster view: [127.0.0.1:37378|1] [127.0.0.1:37378, 127.0.0.1:53149]
15:07:54,855 INFO  [RPCManagerImpl] Received new cluster view: [127.0.0.1:37378|1] [127.0.0.1:37378, 127.0.0.1:53149]

The following channels are started for the HibernateService defined in gatein.ear/02portal.war/WEB-INF/conf/organization/idm-configuration.xml:
DEBUG [org.jboss.cache.RPCManagerImpl] (main) Created Multiplexer Channel for cache cluster optimistic-entity using stack udp
DEBUG [org.jboss.cache.RPCManagerImpl] (main) Created Multiplexer Channel for cache cluster timestamp-cache using stack udp

The configuration for these cache instances would need to be changed to LOCAL cache mode without multiplexer channel.
Comment 1 Martin Weiler 2011-04-11 12:50:36 UTC 
Link: Added: This issue relates to JBEPP-772
Comment 3 hfnukal@redhat.com 2011-04-19 12:11:08 UTC 
Release Notes Docs Status: Added: Not Yet Documented
Release Notes Text: Added: Resolved with new cluster configuration
Comment 4 Scott Mumford 2011-07-11 02:57:15 UTC 
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Removed: Resolved with new cluster configuration Added: It was found that separate instances of epp 5.1 deployed on the same network and started with the 'Default' server profile would communicate as if in a cluster.
This behavior has been resolved with new cluster configuration.
Comment 5 Christoph Hennes 2011-07-12 12:37:05 UTC 
Hello,

we are having the same issue with EPP 5.1. I've taken a look into the dev trunk (see below) to see the current solution. But unfortunately this does not seem to be production-ready ("CHANGEME ...").

Do you have any better solution at the moment, which we could use in 5.1?

Best regards,
Christoph

http://viewvc.jboss.org/cgi-bin/viewvc.cgi/gatein/portal/trunk/web/portal/src/main/webapp/WEB-INF/conf/organization/idm-configuration.xml?view=markup

<property name="hibernate.cache.use_query_cache" value="true"/>
<!--CHANGEME HashtableCacheProvider shold not be used in production env-->
<property name="hibernate.cache.provider_class" value="org.hibernate.cache.HashtableCacheProvider"/>
Comment 6 Scott Mumford 2011-08-22 05:38:38 UTC 
Release Notes Text: Removed: It was found that separate instances of epp 5.1 deployed on the same network and started with the 'Default' server profile would communicate as if in a cluster.
This behavior has been resolved with new cluster configuration. Added: It was found that separate instances of JBoss Enterprise Portal Platform 5.1 deployed on the same network and started with the 'Default' server profile would communicate as if in a cluster.
This behavior has been resolved with new cluster configuration.