-
Bug
-
Resolution: Done
-
Major
-
None
The SE 17 test job[1] is failing for any test where the byteman java agent is added to the server launch. Failures all involve an error report similar to this:
[0m[Server:main-three] OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended [Server:main-three] org.jboss.byteman.agent.Main: unable to open system jar file : /store/work/tc-work/e9bccef30f12678d/testsuite/shared/target/classes [Server:main-three] Exception in thread "main" java.lang.reflect.InvocationTargetException [Server:main-three] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [Server:main-three] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) [Server:main-three] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [Server:main-three] FATAL ERROR in native method: processing of -javaagent failed, processJavaStart failed [Server:main-three] at java.base/java.lang.reflect.Method.invoke(Method.java:568) [Server:main-three] at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:491) [Server:main-three] at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:503) [Server:main-three] Caused by: java.io.FileNotFoundException: /store/work/tc-work/e9bccef30f12678d/testsuite/shared/target/classes (Is a directory) [Server:main-three] at java.base/java.io.RandomAccessFile.open0(Native Method) [Server:main-three] at java.base/java.io.RandomAccessFile.open(RandomAccessFile.java:344) [Server:main-three] at java.base/java.io.RandomAccessFile.<init>(RandomAccessFile.java:259) [Server:main-three] at java.base/java.io.RandomAccessFile.<init>(RandomAccessFile.java:213) [Server:main-three] at java.base/java.util.zip.ZipFile$Source.<init>(ZipFile.java:1312) [Server:main-three] at java.base/java.util.zip.ZipFile$Source.get(ZipFile.java:1277) [Server:main-three] at java.base/java.util.zip.ZipFile$CleanableResource.<init>(ZipFile.java:709) [Server:main-three] at java.base/java.util.zip.ZipFile.<init>(ZipFile.java:243) [Server:main-three] at java.base/java.util.zip.ZipFile.<init>(ZipFile.java:172) [Server:main-three] at java.base/java.util.jar.JarFile.<init>(JarFile.java:347) [Server:main-three] at java.base/java.util.jar.JarFile.<init>(JarFile.java:318) [Server:main-three] at java.base/java.util.jar.JarFile.<init>(JarFile.java:284) [Server:main-three] at org.jboss.byteman.agent.Main.premain(Main.java:185) [Server:main-three] ... 6 more
Most, maybe all of the manualmode testsuite fails for this reason as byteman is added to the standard server launch. The fix there is simple though. None of the tests actually use byteman so it can just be dropped from the server startup config.
These actually pass for me locally when I use a process much like what the CI job does, but of course we want CI to pass.
[1] https://ci.wildfly.org/viewType.html?buildTypeId=WildFlyCore_MainLinuxJdk17
- clones
-
WFCORE-5682 SE 17 tests fail when byteman is used
- Closed
- is incorporated by
-
JBEAP-22582 (7.4.z) Upgrade WildFly Core from 15.0.5.Final-redhat-00001 to 15.0.6.Final-redhat-00001
- Closed