Hide Forgot
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.
Link: Added: This issue relates to JBEPP-772
Release Notes Docs Status: Added: Not Yet Documented Release Notes Text: Added: Resolved with new cluster configuration
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.
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"/>
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.