Bug 1330729 - (6.4.z) EAP is setting up JGroups property that is affecting JGroups in deployment
Summary: (6.4.z) EAP is setting up JGroups property that is affecting JGroups in deplo...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Clustering
Version: 6.4.8
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: CR1
: EAP 6.4.16
Assignee: baranowb
QA Contact: Jiří Bílek
URL:
Whiteboard:
Depends On:
Blocks: 1387585 eap6416-payload
TreeView+ depends on / blocked
 
Reported: 2016-04-26 20:05 UTC by Richa
Modified: 2017-06-22 09:19 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-22 09:19:55 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-4669 0 Major Verified Removed system prop to set CustomLogFactory 2017-11-24 06:30:22 UTC
Red Hat Issue Tracker JDG-114 0 Critical Verified JGroups incompatible with jboss-logging in EAP 6.4 2017-11-24 06:30:22 UTC
Red Hat Issue Tracker JGRP-1475 0 Minor Resolved Convert project to use i18n logging and exceptions 2017-11-24 06:30:22 UTC
Red Hat Issue Tracker JGRP-2060 0 Major Resolved Remove jgroups.logging.log_factory_class or have LogFactory.setCustomLogFactory take precedence to avoid issues with mul... 2017-11-24 06:30:22 UTC

Description Richa 2016-04-26 20:05:59 UTC
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.

Comment 1 Richa 2016-04-26 20:11:16 UTC
This issue is going to block JDG 7.0 release

Comment 5 JBoss JIRA Server 2016-04-29 17:31:57 UTC
Paul Ferraro <paul.ferraro> updated the status of jira JBEAP-4395 to Closed

Comment 9 JBoss JIRA Server 2016-05-09 14:09:48 UTC
Vaclav Dedik <vdedik> updated the status of jira JDG-114 to Coding In Progress

Comment 10 JBoss JIRA Server 2016-05-19 16:30:59 UTC
Jiří Holuša <jholusa> updated the status of jira JDG-114 to Reopened

Comment 11 JBoss JIRA Server 2016-05-24 10:52:38 UTC
Carlo de Wolf <cdewolf> updated the status of jira JBEAP-4395 to Reopened

Comment 12 JBoss JIRA Server 2016-05-24 10:52:48 UTC
Carlo de Wolf <cdewolf> updated the status of jira JBEAP-4395 to Resolved

Comment 13 JBoss JIRA Server 2016-06-08 12:42:50 UTC
Vojtech Juranek <vjuranek> updated the status of jira JDG-114 to Reopened

Comment 19 Radovan STANCEL 2017-05-04 08:36:39 UTC
Correct upstream Jira should be JBEAP-4669 instead of JBEAP-4395

Comment 20 Jiří Bílek 2017-06-08 14:01:34 UTC
Verified with EAP 6.4.16.CP.CR1

Comment 21 Petr Penicka 2017-06-22 09:19:55 UTC
Released on June 20 2017 as part of the EAP 6.4.16 maintenance release.


Note You need to log in before you can comment on or make changes to this bug.