[JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2440:
-------------------------------------
Understood - works for me
> Byteman tests fail when running with the IBM JVM
> ------------------------------------------------
>
> Key: JBTM-2440
> URL: https://issues.jboss.org/browse/JBTM-2440
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Affects Versions: 5.1.1
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.later
>
>
> Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following:
> {code}
> *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009
> Exception in thread "Attachment 59984" Agent failed to start!
> JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102
> {code}
> I will implement a workaround by disabling byteman when testing with this JVM.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris edited comment on JBTM-2454 at 7/8/15 2:27 AM:
---------------------------------------------------------------
[~tomjenkinson], yes it's the tests module. It requires modified standalone-xts.xml, thus was extracted from other XTS junit tests.
It only tests case where default-context-propagation in XTS is disabled.
was (Author: gytis):
[~tomjenkinson], yes it's the tests module. It requires modified standalone-xts.xml, thus was extracted from other XTS junit tests.
> Internal IBM J9 compiler error building XTS
> -------------------------------------------
>
> Key: JBTM-2454
> URL: https://issues.jboss.org/browse/JBTM-2454
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Build System
> Affects Versions: 5.next
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.later
>
>
> On lancel we get the following error. I am unable to reproduce it on my laptop.
> The compiler details are:
> {quote}
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled)
> J9VM - R28_Java8_SR1_20150410_1531_B243669
> JIT - tr.r14.java_20150402_88976.03
> GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS
> J9CL - 20150410_243669)
> JCL - 20150413_01 based on Oracle jdk8u45-b13
> {quote}
> and the build error is:
> {quote}
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes
> An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you.
> java.lang.NullPointerException
> at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142)
> at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758)
> at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162)
> at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.<init>(JavacProcessingEnvironment.java:891)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182)
> at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182)
> at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868)
> at com.sun.tools.javac.main.Main.compile(Main.java:535)
> at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141)
> at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150)
> at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126)
> at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169)
> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785)
> at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:507)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris commented on JBTM-2454:
---------------------------------------
[~tomjenkinson], yes it's the tests module. It requires modified standalone-xts.xml, thus was extracted from other XTS junit tests.
> Internal IBM J9 compiler error building XTS
> -------------------------------------------
>
> Key: JBTM-2454
> URL: https://issues.jboss.org/browse/JBTM-2454
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Build System
> Affects Versions: 5.next
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.later
>
>
> On lancel we get the following error. I am unable to reproduce it on my laptop.
> The compiler details are:
> {quote}
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled)
> J9VM - R28_Java8_SR1_20150410_1531_B243669
> JIT - tr.r14.java_20150402_88976.03
> GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS
> J9CL - 20150410_243669)
> JCL - 20150413_01 based on Oracle jdk8u45-b13
> {quote}
> and the build error is:
> {quote}
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes
> An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you.
> java.lang.NullPointerException
> at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142)
> at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758)
> at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162)
> at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.<init>(JavacProcessingEnvironment.java:891)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182)
> at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182)
> at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868)
> at com.sun.tools.javac.main.Main.compile(Main.java:535)
> at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141)
> at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150)
> at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126)
> at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169)
> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785)
> at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:507)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.... ]
Michael Musgrove edited comment on JBTM-2440 at 7/7/15 6:38 PM:
----------------------------------------------------------------
This issue (JBTM-2440) is to capture the fact that the @BMUnitRunner annotation does not work with the IBM JVM. I don't know how to fix that so I have committed a workaround that adds a profile that disables byteman when running with the ibm JVM. Since I have provided a workaround my preference is to move "fix version" field to 5.later but leave the issue as unresolved.
Whereas issue JBTM-2454 records the fact that the the localjunit-disabled-context-propagation-tests do not compile (at least on lancel) with the IBM compiler and is unrelated to the bug in the @BMUnitRunner annotation.
Remark: the @BMUnitRunner annotation requires the ability to dynamically load an agent but it fails with the IBM JVM. The com.ibm.tools.attach.enable system property ought to allow that behaviour but it still fails and my personal feeling is that there is an issue with the annotation - but, as I say, it is a gut feeling since the annotation implementation seems to work with other JVMs
was (Author: mmusgrov):
This issue (JBTM-2440) is to capture the fact that the @BMUnitRunner annotation does not work with the IBM JVM. I don't know how to fix that so I have committed a workaround that adds a profile that disables byteman when running with the ibm compiler. Since I have provided a workaround my preference is to move "fix version" field to 5.later but leave the issue as unresolved.
Whereas issue JBTM-2454 records the fact that the the localjunit-disabled-context-propagation-tests do not compile (at least on lancel) with the IBM compiler and is unrelated to the bug in the @BMUnitRunner annotation.
Remark: the @BMUnitRunner annotation requires the ability to dynamically load an agent but it fails with the IBM JVM. The com.ibm.tools.attach.enable system property ought to allow that behaviour but it still fails and my personal feeling is that there is an issue with the annotation - but, as I say, it is a gut feeling since the annotation implementation seems to work with other JVMs
> Byteman tests fail when running with the IBM JVM
> ------------------------------------------------
>
> Key: JBTM-2440
> URL: https://issues.jboss.org/browse/JBTM-2440
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Affects Versions: 5.1.1
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.later
>
>
> Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following:
> {code}
> *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009
> Exception in thread "Attachment 59984" Agent failed to start!
> JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102
> {code}
> I will implement a workaround by disabling byteman when testing with this JVM.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-2440:
----------------------------------------
This issue (JBTM-2440) is to capture the fact that the @BMUnitRunner annotation does not work with the IBM JVM. I don't know how to fix that so I have committed a workaround that adds a profile that disables byteman when running with the ibm compiler. Since I have provided a workaround my preference is to move "fix version" field to 5.later but leave the issue as unresolved.
Whereas issue JBTM-2454 records the fact that the the localjunit-disabled-context-propagation-tests do not compile (at least on lancel) with the IBM compiler and is unrelated to the bug in the @BMUnitRunner annotation.
Remark: the @BMUnitRunner annotation requires the ability to dynamically load an agent but it fails with the IBM JVM. The com.ibm.tools.attach.enable system property ought to allow that behaviour but it still fails and my personal feeling is that there is an issue with the annotation - but, as I say, it is a gut feeling since the annotation implementation seems to work with other JVMs
> Byteman tests fail when running with the IBM JVM
> ------------------------------------------------
>
> Key: JBTM-2440
> URL: https://issues.jboss.org/browse/JBTM-2440
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Affects Versions: 5.1.1
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.later
>
>
> Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following:
> {code}
> *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009
> Exception in thread "Attachment 59984" Agent failed to start!
> JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102
> {code}
> I will implement a workaround by disabling byteman when testing with this JVM.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2440:
-----------------------------------
Fix Version/s: 5.later
(was: 5.next)
> Byteman tests fail when running with the IBM JVM
> ------------------------------------------------
>
> Key: JBTM-2440
> URL: https://issues.jboss.org/browse/JBTM-2440
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Affects Versions: 5.1.1
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.later
>
>
> Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following:
> {code}
> *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009
> Exception in thread "Attachment 59984" Agent failed to start!
> JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102
> {code}
> I will implement a workaround by disabling byteman when testing with this JVM.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2454:
-------------------------------------
http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/...
> Internal IBM J9 compiler error building XTS
> -------------------------------------------
>
> Key: JBTM-2454
> URL: https://issues.jboss.org/browse/JBTM-2454
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Build System
> Affects Versions: 5.next
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.later
>
>
> On lancel we get the following error. I am unable to reproduce it on my laptop.
> The compiler details are:
> {quote}
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled)
> J9VM - R28_Java8_SR1_20150410_1531_B243669
> JIT - tr.r14.java_20150402_88976.03
> GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS
> J9CL - 20150410_243669)
> JCL - 20150413_01 based on Oracle jdk8u45-b13
> {quote}
> and the build error is:
> {quote}
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes
> An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you.
> java.lang.NullPointerException
> at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142)
> at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758)
> at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162)
> at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.<init>(JavacProcessingEnvironment.java:891)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182)
> at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182)
> at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868)
> at com.sun.tools.javac.main.Main.compile(Main.java:535)
> at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141)
> at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150)
> at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126)
> at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169)
> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785)
> at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:507)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2454:
-------------------------------------
The module name sounds strange "disabled context propagation" - should this even be tested (or indeed, in the repo), [~gytis]?
> Internal IBM J9 compiler error building XTS
> -------------------------------------------
>
> Key: JBTM-2454
> URL: https://issues.jboss.org/browse/JBTM-2454
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Build System
> Affects Versions: 5.next
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.later
>
>
> On lancel we get the following error. I am unable to reproduce it on my laptop.
> The compiler details are:
> {quote}
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled)
> J9VM - R28_Java8_SR1_20150410_1531_B243669
> JIT - tr.r14.java_20150402_88976.03
> GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS
> J9CL - 20150410_243669)
> JCL - 20150413_01 based on Oracle jdk8u45-b13
> {quote}
> and the build error is:
> {quote}
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes
> An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you.
> java.lang.NullPointerException
> at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142)
> at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758)
> at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162)
> at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.<init>(JavacProcessingEnvironment.java:891)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182)
> at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182)
> at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868)
> at com.sun.tools.javac.main.Main.compile(Main.java:535)
> at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141)
> at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150)
> at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126)
> at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169)
> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785)
> at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:507)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2440:
-------------------------------------
Hi Mike,
Am I right in thinking that this should be fixed, but we still have JBTM-2454? If so it is worth closing this one.
Thanks,
Tom
> Byteman tests fail when running with the IBM JVM
> ------------------------------------------------
>
> Key: JBTM-2440
> URL: https://issues.jboss.org/browse/JBTM-2440
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Affects Versions: 5.1.1
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.next
>
>
> Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following:
> {code}
> *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009
> Exception in thread "Attachment 59984" Agent failed to start!
> JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102
> {code}
> I will implement a workaround by disabling byteman when testing with this JVM.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months