Greetings Evgeny, I can confirm that the workaround of downgrading to 0.8.2
allows us to avoid the error and run the tests normally - provided *all* of
the following JVM startup parameters are added to the integration tests
startup of wildfly/jboss: (normally all on one line, formatted here for
readability)
-Djboss.modules.system.pkgs=org.jboss.logmanager
-Xbootclasspath/a:
${env.JBOSS_HOME}/modules/system/layers/base/org/jboss/logmanager/main/
jboss-logmanager-2.1.14.Final.jar;
${env.JBOSS_HOME}/modules/system/layers/base/org/wildfly/common/main/
wildfly-common-1.5.1.Final.jar
-Dsun.util.logging.disableCallerCheck=true
-Djava.util.logging.manager=org.jboss.logmanager.LogManager
I've regression tested this with both Hotspot and J9 (on OpenJDK 11 build
11.0.5+10) - On windows x64 and the above parameters are compatible with
both VM runtimes
Thank you very much for the assistance, please let me know if there is
anything else I can do to help. I would be happy to invest the time to
create a simple test project that demonstrates the error and use that to
file a properly documented issue in github, if that is helpful. I can also
attempt to verify whether this occurs on a couple of different linuxes
(though I see no reason why it should be platform-specific).
Thanks again,
-a
On Monday, January 13, 2020 at 5:11:02 PM UTC-6, Evgeny Mandrikov wrote:
>
> Hi,
>
> Thank you for this report. I'm able to reproduce issue and it
> certainly relates to https://github.com/jacoco/jacoco/pull/829 which was
> implemented in JaCoCo version 0.8.3, so can you try to use 0.8.2 as a
> workaround while we investigate it further?
>
>
> Regards,
> Evgeny
>
>
>
> On Mon, Jan 13, 2020 at 9:58 PM <[email protected] <javascript:>> wrote:
>
>> Using Java 11, we've found that our integration tests using WildFly 18
>> run correctly and provide the instrumentation and reports when using the
>> OpenJDK11-Hotspot VM JDK.
>>
>> However, if we run the same build with the OpenJDK-11-J9 VM (the eclipse
>> J9 runtime) - this occurs:
>>
>> INFO: Starting container with: [C:\Development\Java\JDK\bin\java,
>> -D[Standalone], -Xmx10G,
>> -Djava.library.path=C:\\Development\\WildFly\\standalone\\lib,
>> -javaagent:C:\\Development\\portal\\libs\\DB\\target\\jacocoagent-0.8.5.jar=destfile=C:\\Development\\portal\\libs\\DB\\target\\jacoco.exec,
>>
>> -ea, -Djboss.home.dir=C:\Development\WildFly,
>> -Dorg.jboss.boot.log.file=C:\Development\WildFly\standalone\log\server.log,
>> -Dlogging.configuration=file:C:\Development\WildFly\standalone\configuration\logging.properties,
>>
>> -jar, C:\Development\WildFly\jboss-modules.jar, -mp,
>> C:\Development\WildFly\modules, org.jboss.as.standalone,
>> -Djboss.home.dir=C:\Development\WildFly,
>> -Djboss.server.base.dir=C:\Development\WildFly\standalone,
>> -Djboss.server.log.dir=C:\Development\WildFly\standalone\log,
>> -Djboss.server.config.dir=C:\Development\WildFly\standalone\configuration]
>> Exception in thread "main" java.lang.NoClassDefFoundError:
>> java.lang.$JaCoCo
>> at org.jboss.logmanager.LogManager.$jacocoInit(LogManager.java)
>> at org.jboss.logmanager.LogManager.<clinit>(LogManager.java)
>> at java.base/java.lang.J9VMInternals.newInstanceImpl(Native
>> Method)
>> at java.base/java.lang.Class.newInstance(Class.java:2082)
>> at
>> java.logging/java.util.logging.LogManager$1.run(LogManager.java:239)
>> at
>> java.logging/java.util.logging.LogManager$1.run(LogManager.java:223)
>> at
>> java.base/java.security.AccessController.doPrivileged(AccessController.java:678)
>> at
>> java.logging/java.util.logging.LogManager.<clinit>(LogManager.java:223)
>> at org.jboss.modules.Main.main(Main.java:523)
>> Caused by: java.lang.ClassNotFoundException: java.lang.$JaCoCo from
>> [Module "org.jboss.logmanager" version 2.1.14.Final from local module
>> loader @4f93e763 (finder: local module finder @cbe6fdc3 (roots:
>> C:\Development\WildFly\modules,C:\Development\WildFly\modules\system\layers\base))]
>> at
>> org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255)
>> at
>> org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
>> at
>> org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
>> at
>> org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
>> ... 9 more
>>
>> We had a very similar issue with another instrumentation library on our
>> production machines (DynaTrace app monitoring) but were able to fix that by
>> modifying the startup parameters (adding the logging/modules/Xbootclasspath
>> options you see above).
>>
>> Have we stumbled into an incompatibility with Jacoco, or just not hit on
>> the exact configuration syntax? Please advise so I can either give up,
>> provide more info, or file a bug report.
>> Regards and thanks for your time,
>> -a
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "JaCoCo and EclEmma Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jacoco/7dc56828-288e-4896-ab24-62c20919555f%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/jacoco/7dc56828-288e-4896-ab24-62c20919555f%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
--
You received this message because you are subscribed to the Google Groups
"JaCoCo and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jacoco/27d26906-6690-4408-a4f8-e71e30b150ac%40googlegroups.com.
