[ https://issues.apache.org/jira/browse/ARTEMIS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114979#comment-15114979 ]
ASF GitHub Bot commented on ARTEMIS-359: ---------------------------------------- GitHub user mnovak1 opened a pull request: https://github.com/apache/activemq-artemis/pull/342 ARTEMIS-359 - test suite fix - IBM JDK 6/7/8 does not allow byteman a… …gent to modify classes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mnovak1/activemq-artemis master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/342.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #342 ---- commit 65ccf56c78026b9e00a6e9dfcfca74b3b735bec9 Author: Miroslav Novak <mno...@redhat.com> Date: 2016-01-25T09:47:14Z ARTEMIS-359 - test suite fix - IBM JDK 6/7/8 does not allow byteman agent to modify classes. ---- > [TestSuite] IBM JDK does not allow to instrument classes > -------------------------------------------------------- > > Key: ARTEMIS-359 > URL: https://issues.apache.org/jira/browse/ARTEMIS-359 > Project: ActiveMQ Artemis > Issue Type: Bug > Affects Versions: 1.1.0 > Reporter: Miroslav Novak > > IBM JDK 6/7/8 does not allow byteman agent to modify classes. For example > "extra-tests" will fail with following exception: > {code} > Running > org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest > byteman jar is > /home/mnovak/.m2/repository/org/jboss/byteman/byteman/2.2.0/byteman-2.2.0.jar > com.ibm.tools.attach.AttachNotSupportedException: acknowledgement timeout > from 21654 on port 42521 > at > com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:401) > at > com.ibm.tools.attach.javaSE.VirtualMachineImpl.attachTarget(VirtualMachineImpl.java:94) > at > com.ibm.tools.attach.javaSE.AttachProviderImpl.attachVirtualMachine(AttachProviderImpl.java:37) > at > ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:55) > at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231) > at org.jboss.byteman.agent.install.Install.attach(Install.java:374) > at org.jboss.byteman.agent.install.Install.install(Install.java:113) > at > org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340) > at > org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472) > at > org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.net.SocketTimeoutException: Accept timed out > at > java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:445) > at java.net.ServerSocket.implAccept(ServerSocket.java:620) > at java.net.ServerSocket.accept(ServerSocket.java:579) > at > com.ibm.tools.attach.javaSE.VirtualMachineImpl.tryAttachTarget(VirtualMachineImpl.java:396) > ... 17 more > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 291.094 sec > <<< FAILURE! - in > org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest > org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest(org.apache.activemq.artemis.tests.extras.byteman.ActiveMQMessageHandlerTest) > Time elapsed: 291.094 sec <<< ERROR! > com.sun.tools.attach.AttachNotSupportedException: acknowledgement timeout > from 21654 on port 42521 > at > ibm.tools.attach.J9AttachProvider.attachVirtualMachine(J9AttachProvider.java:60) > at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:231) > at org.jboss.byteman.agent.install.Install.attach(Install.java:374) > at org.jboss.byteman.agent.install.Install.install(Install.java:113) > at > org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:340) > at > org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:472) > at > org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:98) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)