-
Bug
-
Resolution: Not a Bug
-
Major
-
7.1.3.CR1, 7.1.4.CR1
-
None
Logmanager tests FilterTests and LoggerTests started to fail on ibm-java-1.8 after Logmanager upgrade from 2.0.8.Final-redhat-1 to 2.0.10.Final (JBEAP-14446). All the test methods are failing with the error message
The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
The stacktrace is:
java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") at org.jboss.logmanager.Logger.getLogger(Logger.java:57) at org.jboss.logmanager.FilterTests.testAcceptAllFilter(FilterTests.java:56) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:508) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:379) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:340) at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:413)
This property (java.util.logging.manager) is set for the tests in the maven-surefire-plugin:
<java.util.logging.manager>org.jboss.logmanager.LogManager</java.util.logging.manager>
The tests were also ran on the previous java version with the same results.
Link for the server log from the last run:
https://eap-cp-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-71x-jboss-logmanager-upstream-ts-matrix-rhel/jdk=ibm-java-1.8,label_exp=RHEL6&&x86/lastCompletedBuild/testReport/org.jboss.logmanager/FilterTests/testAcceptAllFilter/
It might be an unrelated issue, but another three tests are failing now with the "java.net.ConnectException: Connection refused (Connection refused)" exception (PeriodicRotatingFileHandlerTests, PeriodicSizeRotatingFileHandlerTests and SizeRotatingFileHandlerTests).
Stacktrace:
java.net.ConnectException: Connection refused (Connection refused) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:380) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:236) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:218) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403) at java.net.Socket.connect(Socket.java:666) at java.net.Socket.connect(Socket.java:606) at java.net.Socket.<init>(Socket.java:469) at java.net.Socket.<init>(Socket.java:239) at org.jboss.byteman.agent.submit.Submit$Comm.<init>(Submit.java:881) at org.jboss.byteman.agent.submit.Submit.submitRequest(Submit.java:787) at org.jboss.byteman.agent.submit.Submit.addScripts(Submit.java:603) at org.jboss.byteman.contrib.bmunit.BMUnit.loadScriptText(BMUnit.java:268) at org.jboss.byteman.contrib.bmunit.BMUnitRunner$10.evaluate(BMUnitRunner.java:369) at org.jboss.byteman.contrib.bmunit.BMUnitRunner$6.evaluate(BMUnitRunner.java:241) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:75) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:379) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:340) at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:413)
- is related to
-
-
- Resolved
-
