[jboss-jira] [JBoss JIRA] (WFCORE-3797) Logging Subsystem test failures on IBM jdk

[Petr Kremensky (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Petr Kremensky updated WFCORE-3797:
-----------------------------------
    Steps to Reproduce: 
{noformat}# switch to IBM jdk
mvn test -pl logging{noformat}

  was:
# switch to IBM jdk
mvn test -pl logging



> Logging Subsystem test failures on IBM jdk
> ------------------------------------------
>
>                 Key: WFCORE-3797
>                 URL: https://issues.jboss.org/browse/WFCORE-3797
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Logging, Test Suite
>    Affects Versions: 5.0.0.Alpha1, 5.0.0.Alpha2, 5.0.0.Alpha3, 5.0.0.Alpha4
>         Environment: {noformat}
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 1.8.0_161, vendor: IBM Corporation
> Java home: /usr/lib/java/ibm-java-8.0-5.11/jre
> {noformat}
>            Reporter: Petr Kremensky
>            Assignee: James Perkins
>
> WildFly: Logging Subsystem unit tests fails on IBM jdk with:
> {noformat}
> java.lang.IllegalStateException: WFLYLOG0078: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> 	at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:168)
> 	at org.jboss.as.subsystem.test.TestModelControllerService.preBoot(TestModelControllerService.java:158)
> 	at org.jboss.as.model.test.ModelTestModelControllerService.boot(ModelTestModelControllerService.java:264)
> 	at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:419)
> 	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:372)
> 	at java.lang.Thread.run(Thread.java:811)
> {noformat}
> The test works fine with *4.0.0.Final*, starts failing in *5.0.0.Alpha1*.
> This doens't look like a functional issue to me as I was able to workaround the issue by either running the test with the older surefire instance ( -Dversion.surefire.plugin=2.19 is the last working ) or by extending {{surefire.system.args}} in pom.xml with {{-Djava.util.logging.manager=org.jboss.logmanager.LogManager}}. The other however produces the following warnings upon test execution
> {noformat}
> ...
> [WARNING] The system property java.util.logging.manager is configured twice! The property appears in <argLine/> and any of <systemPropertyVariables/>, <systemProperties/> or user property.
> [INFO] 
> [INFO] -------------------------------------------------------
> [INFO]  T E S T S
> [INFO] -------------------------------------------------------
> [INFO] Running org.jboss.as.logging.HandlerLegacyOperationsTestCase
> [WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 1. See FAQ web page and the dump file /home/pkremens/devel/wildfly-core/logging/target/surefire-reports/2018-05-03T13-49-32_779-jvmRun1.dumpstream
> ...
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)