Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-3797

Logging Subsystem test failures on IBM jdk

    XMLWordPrintable

Details

    Description

      WildFly: Logging Subsystem unit tests fails on IBM jdk with:

      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)
      

      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

      ...
      [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
      ...
      

      Attachments

        Issue Links

          Activity

            People

              jperkins-rhn James Perkins
              pkremens@redhat.com Petr Kremensky (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: