Bug 793703 (JBEPP-778) - Call RuntimeConfig.setMuxChannelFactory for the JBoss Cache instances created by PicketLink IDM
Summary: Call RuntimeConfig.setMuxChannelFactory for the JBoss Cache instances created...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-778
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal
Version: 5.1.0.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0.ER06
Assignee: Boleslaw Dawidowicz
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-26 21:31 UTC by Martin Weiler
Modified: 2012-02-29 22:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-26 10:41:41 UTC
Type: Task

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 793658 0 high CLOSED Leverage the EAP parameter jboss.default.jgroups.stack to make switching to TCP easier 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 793862 0 high CLOSED EPP52-EID_103: JBoss Cache/jGroups review 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 794144 0 high CLOSED Support for shared transport in JGroups configuration 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBEPP-778 0 None None None Never

Internal Links: 793658 793862 794144

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
Note You need to log in before you can comment on or make changes to this bug.