Hide Forgot
Description of problem: During the startup of EAP 6.4, the JGroups property "jgroups.logging.log_factory_class" in JGroupsExtension, see the code below: // Workaround for JGRP-1475 // Configure JGroups to use jboss-logging. static { PrivilegedAction<Void> action = new PrivilegedAction<Void>() { @Override public Void run() { if (System.getProperty(Global.CUSTOM_LOG_FACTORY) == null) { System.setProperty(Global.CUSTOM_LOG_FACTORY, LogFactory.class.getName()); } return null; } }; AccessController.doPrivileged(action); } If the deployment uses other version of JGroups (for instance because of Infinispan), it might cause troubles (and it actually does) that you are affected by the property being set, therefore even your deployed JGroups picks it up.
This issue is going to block JDG 7.0 release
Paul Ferraro <paul.ferraro> updated the status of jira JBEAP-4395 to Closed
Vaclav Dedik <vdedik> updated the status of jira JDG-114 to Coding In Progress
Jiří Holuša <jholusa> updated the status of jira JDG-114 to Reopened
Carlo de Wolf <cdewolf> updated the status of jira JBEAP-4395 to Reopened
Carlo de Wolf <cdewolf> updated the status of jira JBEAP-4395 to Resolved
Vojtech Juranek <vjuranek> updated the status of jira JDG-114 to Reopened
Correct upstream Jira should be JBEAP-4669 instead of JBEAP-4395
Verified with EAP 6.4.16.CP.CR1
Released on June 20 2017 as part of the EAP 6.4.16 maintenance release.