Bug 793704 (JBEPP-779)

Summary:	Call RuntimeConfig.setMuxChannelFactory for the MOPSessionManager JBoss Cache instance
Product:	[JBoss] JBoss Enterprise Portal Platform 5	Reporter:	Martin Weiler <mweiler>
Component:	Portal	Assignee:	mposolda
Status:	CLOSED WONTFIX	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.1.0.GA, 5.1.1.DEV01	CC:	epp-bugs, hfnukal, mposolda, mweiler, nicolas.filotto, prabhat.jha, theute
Target Milestone:	---
Target Release:	5.2.0.ER06
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEPP-779
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-26 10:45:34 UTC	Type:	Task
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-26 21:32:04 UTC

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.

Comment 1 Martin Weiler 2011-01-26 21:33:03 UTC

Link: Added: This issue related JBEPP-736

Comment 5 hfnukal@redhat.com 2011-04-14 13:59:10 UTC

Release Notes Docs Status: Added: Needs More Info
Release Notes Text: Added: Configuration moved from jar file to portal.war.

Comment 6 Thomas Heute 2011-04-29 07:38:30 UTC

Release Notes Docs Status: Removed: Needs More Info Added: Not Required

Comment 7 mposolda 2011-05-06 15:08:32 UTC

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 ?

Comment 9 Nicolas Filotto 2011-05-06 18:39:25 UTC

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.

Comment 10 Prabhat Jha 2011-05-06 18:46:41 UTC

Nicolas, I am fine with what you are saying. I think your previous comment needs to be mentioned under release notes.

Comment 11 Prabhat Jha 2011-05-06 18:47:50 UTC

Release Notes Docs Status: Removed: Not Required Added: Not Yet Documented

Comment 12 Thomas Heute 2011-05-09 08:42:33 UTC

I moved it to 5.2, we'll need an in depth analysis/alignment of cache/jgroups configuration

Comment 13 Thomas Heute 2011-05-18 10:20:43 UTC

Link: Added: This issue is related to JBEPP-935

Comment 14 mposolda 2011-09-27 13:15:03 UTC

Link: Added: This issue is related to JBEPP-1210

Comment 15 mposolda 2011-10-26 10:45:34 UTC

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.

Comment 17 Jared MORGAN 2011-11-29 22:32:28 UTC

Release Notes Docs Status: Removed: Not Yet Documented Added: Not Required

Comment 19 Jared MORGAN 2011-11-29 22:33:13 UTC

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.