Bug 793703 (JBEPP-778)

Summary:	Call RuntimeConfig.setMuxChannelFactory for the JBoss Cache instances created by PicketLink IDM
Product:	[JBoss] JBoss Enterprise Portal Platform 5	Reporter:	Martin Weiler <mweiler>
Component:	Portal	Assignee:	Boleslaw Dawidowicz <bdawidow>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.1.0.GA	CC:	boleslaw.dawidowicz, epp-bugs, hfnukal, mposolda
Target Milestone:	---
Target Release:	5.2.0.ER06
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEPP-778
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-26 10:41:41 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:31:42 UTC

Help Desk Ticket Reference: https://na7.salesforce.com/500A0000005ezKT
project_key: JBEPP

In order to change the jgroups configuration for the cache instances created by PicketLink to use a different stack (for instance to switch to TCP), it would be nice to support the following configuration in conf/organization/picketlink-idm/jboss-cache-cluster.xml:

  <clustering mode="replication" clusterName="${jboss.partition.name:DefaultPartition}-idm-cluster">
      <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. 

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 2 boleslaw.dawidowicz 2011-04-06 13:36:17 UTC

Link: Added: This issue depends GTNPORTAL-1853

Comment 3 boleslaw.dawidowicz 2011-04-19 12:30:30 UTC

Some work related to this issue was commited as part of GTNPORTAL-1853

https://fisheye.jboss.org/changelog/gatein?cs=6168

Still Martin reported that things are not picked up properly, but there is workaround available on the config level. I guess we could pospone this one after 5.1.1?

Comment 4 boleslaw.dawidowicz 2011-04-19 12:30:31 UTC

Some work related to this issue was commited as part of GTNPORTAL-1853

https://fisheye.jboss.org/changelog/gatein?cs=6168

Still Martin reported that things are not picked up properly, but there is workaround available on the config level. I guess we could pospone this one after 5.1.1?

Comment 5 Thomas Heute 2011-05-18 10:20:49 UTC

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

Comment 6 boleslaw.dawidowicz 2011-08-16 10:17:29 UTC

This needs further investigation and we may not be able to look at it at the moment.

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

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

Comment 8 mposolda 2011-10-26 10:38:44 UTC

Link: Added: This issue relates to JBEPP-1210

Comment 9 mposolda 2011-10-26 10:41:41 UTC

Release Notes Text: Added: Now we are using shared transport for jgroups instead of multiplexer. it's possible to use multiplexer if needed, but not recommended. This has been fixed in rev7870 with fix to JBEPP-1210

Comment 10 Thomas Heute 2011-11-17 15:07:17 UTC

Release Notes Docs Status: Added: Not Required