[ https://issues.jboss.org/browse/WFCORE-4525?page=com.atlassian.jira.plugi... ] Richard Opalka commented on WFCORE-4525: ---------------------------------------- I debugged this problem and I identified some of these tests fail because of late system properties setup in ForkedBooter class when surefire plugin runs on top of IBM JDK. ForkedBooter sets up system properties for forked process on line 95 in method ForkedBooter.setupBooter() method. But on IBM JDK (see ibm-jdk8.png) the Java system logger is initialized before jboss logging properties are setup (this happens on line 94 in method ForkedBooter.setupBooter()) Detailed explanation: * ForkedBooter.isDebugging() method call on line 94 behaves differently on IBM JDK and on Oracle JDK from java system logger configuration point of view. * Oracle's ManagementFactory.getRuntimeMXBean() method invocation doesn't force java system logging initialization because its MX bean isn't using logging. * But IBM's ManagementFactory.getRuntimeMXBean() method invocation forces java system logging initialization because its MX bean is using logging. The problem is system properties are configured for forked process on line 95 in ForkedBooter (see forked-booter.png) and so on IBM JDK jboss logging properties are not configured which results in Apache Log4j being used. On Oracle JDK JBoss log manager is used instead. On Oracle JDK system properties are properly set up and later used for logging configuration (see oracle-jdk.png). -- This message was sent by Atlassian Jira (v7.12.1#712002)