Hide Forgot
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000005ezKT project_key: JBEPP In order to change the jgroups configuration for the MOPSessionManager cache instance to use a different stack (for instance to switch to TCP), it would be nice to support the following configuration: <clustering mode="replication" clusterName="${jboss.partition.name:DefaultPartition}-gatein"> <jgroupsConfig multiplexerStack="jcr.stack.tcp" /> </clustering> But this will only work if setMuxChannelFactory is called as in http://anonsvn.jboss.org/repos/exo-jcr/jcr/trunk/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/jbosscache/ExoJBossCacheFactory.java, which is not happening in org.exoplatform.services.cache.impl.jboss.ExoCacheFactoryImpl. Otherwise, the full notation (<jgroupsConfig><TCP ...the full stack config/></jgroupsConfig>) would need to be repeated in the config file.
Link: Added: This issue related JBEPP-736
Release Notes Docs Status: Added: Needs More Info Release Notes Text: Added: Configuration moved from jar file to portal.war.
Release Notes Docs Status: Removed: Needs More Info Added: Not Required
I am reopening since the main purpose of this Jira (setting multiplexer channel for MOPSessionManager) is not done. Shouldn't we create JIRA in eXo kernel for multiplexer channel support ?
If I were you, I would forget the multiplexer, it is deprecated in JGroups and will be removed soon, use the shared transport instead (http://www.jgroups.org/manual/html/user-advanced.html). About the eXo Kernel, AFAIK, the shared transport can be used without modifying a line of code just by configuration. BTW, Supporting the Multiplexer of JGroups in eXo JCR was my mistake, I would like to avoid doing the same mistake in eXo Kernel.
Nicolas, I am fine with what you are saying. I think your previous comment needs to be mentioned under release notes.
Release Notes Docs Status: Removed: Not Required Added: Not Yet Documented
I moved it to 5.2, we'll need an in depth analysis/alignment of cache/jgroups configuration
Link: Added: This issue is related to JBEPP-935
Link: Added: This issue is related to JBEPP-1210
Release Notes Text: Removed: Configuration moved from jar file to portal.war. Added: We fixed it by using of shared transport instead of multiplexer, as multiplexer is not recommended. eXo kernel does not support multiplexer for caches created by CacheServiceImpl (MOPSessionManager, NavigationService, DescriptionService) and they don't want to add it, as it's deprecated for JGroups. Shared transport is enabled in JBEPP-1210 with fix from revision 7870.
Release Notes Docs Status: Removed: Not Yet Documented Added: Not Required
Release Notes Text: Removed: We fixed it by using of shared transport instead of multiplexer, as multiplexer is not recommended. eXo kernel does not support multiplexer for caches created by CacheServiceImpl (MOPSessionManager, NavigationService, DescriptionService) and they don't want to add it, as it's deprecated for JGroups. Shared transport is enabled in JBEPP-1210 with fix from revision 7870.