[infinispan-issues] [JBoss JIRA] (ISPN-3076) Infinispan should enable use of log4j2

[Dan Berindei (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989093#comment-12989093 ] 

Dan Berindei commented on ISPN-3076:
------------------------------------

I've started investigating this again for the test suite, as I've started seeing log messages delayed by several minutes (!) in the CI logs, and I think delays in log4j may :

{noformat}
15:37:06,079 INFO  (testng-MergeViewTest:) [UnitTestTestNGListener] Starting test testMergeViewHappens(org.infinispan.notifications.MergeViewTest)
15:45:57,491 ERROR (testng-MergeViewTest:) [UnitTestTestNGListener] Test testMergeViewHappens(org.infinispan.notifications.MergeViewTest) failed.
java.lang.RuntimeException: Timed out before caches had complete views.  Expected 2 members in each view.  Views are as follows: [[MergeViewTest-NodeA-7118], [MergeViewTest-NodeB-19815]]
15:37:19,720 DEBUG (Timer-2,MergeViewTest-NodeA-7118:) [MERGE3] I (MergeViewTest-NodeA-7118) will be the merge leader
{noformat}

[~sannegrinovero] I only intend to change the test suite to use log4j2, production code will still log through jboss-logging and it will support anything that jboss-logging supports. Bela has already changed the JGroups test suite to use log4j2, so I'm confident it won't cause problems.

> Infinispan should enable use of log4j2
> --------------------------------------
>
>                 Key: ISPN-3076
>                 URL: https://issues.jboss.org/browse/ISPN-3076
>             Project: Infinispan
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Core
>    Affects Versions: 5.2.5.Final, 6.0.0.Final
>         Environment: Any
>            Reporter: Divya Mehra
>            Assignee: Dan Berindei
>
> log4j locks up on a certain amount of load, especially under concurrent access. The recommendation was to move up to log4j2. This can be done by removing
> 1 JAR (log4j.jar) and adding 2 JARs (log4j-bridge and log4j-core.jar). 
> Also refer: https://issues.jboss.org/browse/ISPN-2976



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)