Hide Forgot
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000005ezKT project_key: JBEPP The two JBoss Cache instances created by PicketLink are using the same cluster names, as they are both pointing to the same config file in idm-configuration.xml: <value-param profiles="cluster"> <name>apiCacheConfig</name> <value>war:/conf/organization/picketlink-idm/jboss-cache-cluster.xml</value> </value-param> <value-param profiles="cluster"> <name>storeCacheConfig</name> <value>war:/conf/organization/picketlink-idm/jboss-cache-cluster.xml</value> </value-param> This can lead to conflicts as the same JBoss instance is joining the same channel twice, so either two different config files are provided, or a different 'clusterName' attribute is being used in the jboss-cache-cluster.xml config file.
Link: Added: This issue related JBEPP-736
Link: Added: This issue depends GTNPORTAL-1853
Resolved with JBEPP-779
Reopening as the jboss-cache-api-cluster.xml and jboss-cache-store-cluster.xml files are missing from EPP_5_1_Branch
Attaching patch proposal to add the two missing *cluster.xml files for IDM.
Attachment: Added: JBEPP-780.patch
Release Notes Docs Status: Added: Documented as Known Issue Release Notes Text: Added: Two JBoss Cache instances used single config file. Two config files were created and configurationn was customized.
Should this still be marked as a Known Issue? The problem causing the issue seems to have been corrected and the JIRA re-opened for a different reason (if I'm understanding the comments correctly)
Release Notes Text: Removed: Two JBoss Cache instances used single config file. Two config files were created and configurationn was customized. Added: Cause: The two JBoss Cache instances created by PicketLink were calling on the same configuration file in idm-configuration.xml and, as a result, were using the same cluster names. Consequence: This could lead to conflicts as the same JBoss Cache instance could join the same channel twice. Fix: Two configuration files were created and added to the distribution package and the Portal configuration was customized to call on the different files. Result: JBoss Cache instances can now run simultaneously without conflict.
Release Notes Docs Status: Removed: Documented as Known Issue Added: Documented as Resolved Issue
Release Notes Text: Removed: Cause: The two JBoss Cache instances created by PicketLink were calling on the same configuration file in idm-configuration.xml and, as a result, were using the same cluster names. Consequence: This could lead to conflicts as the same JBoss Cache instance could join the same channel twice. Fix: Two configuration files were created and added to the distribution package and the Portal configuration was customized to call on the different files. Result: JBoss Cache instances can now run simultaneously without conflict. Added: The two JBoss Cache instances created by PicketLink were calling on the same configuration file in idm-configuration.xml and, as a result, were using the same cluster names. This could lead to conflicts as the same JBoss Cache instance could join the same channel twice. Separate configuration files were added to the distribution package and the Portal configuration was customized to call on the different files. JBoss Cache instances can now run simultaneously without conflict.
What about removing the file web/portal/src/main/webapp/WEB-INF/conf/organization/picketlink-idm/jboss-cache-cluster.xml ? I think this can be removed because not-cluster profile is using "jboss-cache.xml" and cluster profile is using two mentioned files "jboss-cache-api-cluster.xml" and "jboss-cache-store-cluster.xml" . I am not reopening since it is only a minor thing.
Reopening as discussed with Honza. More info in previous comment.
Remove unused file
Link: Added: This issue is related to GTNPORTAL-2234