[jbossts-issues] [JBoss JIRA] (JBTM-3305) Quickstart transactionaldriver-standalone module throws an exception when build with JDK11
Mayank Kunwar (Jira)
issues at jboss.org
Tue Apr 28 11:46:08 EDT 2020
[ https://issues.redhat.com/browse/JBTM-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mayank Kunwar updated JBTM-3305:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Quickstart transactionaldriver-standalone module throws an exception when build with JDK11
> ------------------------------------------------------------------------------------------
>
> Key: JBTM-3305
> URL: https://issues.redhat.com/browse/JBTM-3305
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Reporter: Mayank Kunwar
> Assignee: Mayank Kunwar
> Priority: Major
>
> When running Quickstart transactionaldriver-standalone on JDK11 with below command throws exception.
> mvn clean install
> java.io.IOException: Can not attach to current VM
> at jdk.attach/sun.tools.attach.HotSpotVirtualMachine.<init>(HotSpotVirtualMachine.java:75)
> at jdk.attach/sun.tools.attach.VirtualMachineImpl.<init>(VirtualMachineImpl.java:57)
> at jdk.attach/sun.tools.attach.AttachProviderImpl.attachVirtualMachine(AttachProviderImpl.java:58)
> at jdk.attach/com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:207)
> at org.jboss.byteman.agent.install.Install.attach(Install.java:451)
> at org.jboss.byteman.agent.install.Install.install(Install.java:161)
> at org.jboss.byteman.agent.install.Install.install(Install.java:116)
> at org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:516)
> at org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:669)
> at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:73)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the jbossts-issues
mailing list