[jbossts-issues] [JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM

[ 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 -- This message was sent by Atlassian JIRA (v6.3.15#6346)