[JBoss JIRA] (JBTM-2444) jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2444?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-2444:
----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/quickstart/pull/142
> jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ
> ---------------------------------------------------------------------------------------------
>
> Key: JBTM-2444
> URL: https://issues.jboss.org/browse/JBTM-2444
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Documentation
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Priority: Blocker
> Fix For: 5.next
>
>
> {code}
> Running org.jboss.narayana.quickstarts.jta.TestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 18.563 sec <<< FAILURE!
> Results :
> Tests in error:
> org.jboss.narayana.quickstarts.jta.TestCase: Cannot deploy: test.war
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> {code}
> The log file says:
> {code}
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /home/hudson/workspace/narayana-quickstarts/wildfly-10.0.0.Alpha4-SNAPSHOT/standalone/tmp/vfs/temp/temp174d29cf17a7dbea/content-a7b7e754b2627502/WEB-INF/test-jms.xml
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[23,1]
> Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment'"}}
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
> at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
> at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
> ... 96 more
> {code}
> Which leads me to believe it is likely due to the parsing in test-jms.xml.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (JBTM-2445) Back port JBTM-692 into EAP 5.2
by Tom Ross (JIRA)
Tom Ross created JBTM-2445:
------------------------------
Summary: Back port JBTM-692 into EAP 5.2
Key: JBTM-2445
URL: https://issues.jboss.org/browse/JBTM-2445
Project: JBoss Transaction Manager
Issue Type: Support Patch
Components: JTA, JTS
Affects Versions: 4.6.1.CP13
Environment: JBoss EAP 5.2.0.GA
Reporter: Tom Ross
Assignee: Tom Ross
Back port of JBTM-692
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (JBTM-2440) Disable byteman tests 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:
----------------------------------------
I do recall - we disable the tests because byteman is known not to work with the IBM J9 compiler. So the fix is just to go back to not running the tests on J9 and figure out how to make byteman work with J9 as an optional task.
> Disable byteman tests 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: Optional
> 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)
9 years, 5 months
[JBoss JIRA] (JBTM-2440) Disable byteman tests 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:
-----------------------------------
Priority: Optional (was: Major)
> Disable byteman tests 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: Optional
> 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)
9 years, 5 months
[JBoss JIRA] (JBTM-2440) Disable byteman tests 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:
----------------------------------------
I not certain but diff'ing the config between now and the last successful build reveals that the tests were disabled NARAYANA_TESTS=0 on the sucessful build
> Disable byteman tests 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
> 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)
9 years, 5 months
[JBoss JIRA] (JBTM-2444) jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2444?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2444:
-------------------------------------
Consistently failing so it is a blocker for 5.2 - [~gytis], please can you have a look as a matter of urgency?
> jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ
> ---------------------------------------------------------------------------------------------
>
> Key: JBTM-2444
> URL: https://issues.jboss.org/browse/JBTM-2444
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Documentation
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Priority: Blocker
> Fix For: 5.next
>
>
> {code}
> Running org.jboss.narayana.quickstarts.jta.TestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 18.563 sec <<< FAILURE!
> Results :
> Tests in error:
> org.jboss.narayana.quickstarts.jta.TestCase: Cannot deploy: test.war
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> {code}
> The log file says:
> {code}
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /home/hudson/workspace/narayana-quickstarts/wildfly-10.0.0.Alpha4-SNAPSHOT/standalone/tmp/vfs/temp/temp174d29cf17a7dbea/content-a7b7e754b2627502/WEB-INF/test-jms.xml
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[23,1]
> Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment'"}}
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
> at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
> at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
> ... 96 more
> {code}
> Which leads me to believe it is likely due to the parsing in test-jms.xml.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (JBTM-2444) jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ
by Tom Jenkinson (JIRA)
Tom Jenkinson created JBTM-2444:
-----------------------------------
Summary: jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ
Key: JBTM-2444
URL: https://issues.jboss.org/browse/JBTM-2444
Project: JBoss Transaction Manager
Issue Type: Feature Request
Components: Documentation
Reporter: Tom Jenkinson
Assignee: Gytis Trikleris
Priority: Blocker
Fix For: 5.next
{code}
Running org.jboss.narayana.quickstarts.jta.TestCase
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 18.563 sec <<< FAILURE!
Results :
Tests in error:
org.jboss.narayana.quickstarts.jta.TestCase: Cannot deploy: test.war
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
{code}
The log file says:
{code}
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /home/hudson/workspace/narayana-quickstarts/wildfly-10.0.0.Alpha4-SNAPSHOT/standalone/tmp/vfs/temp/temp174d29cf17a7dbea/content-a7b7e754b2627502/WEB-INF/test-jms.xml
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[23,1]
Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment'"}}
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
... 96 more
{code}
Which leads me to believe it is likely due to the parsing in test-jms.xml.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (JBTM-2444) jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2444?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2444:
-------------------------------------
http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-quicksta...
> jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ
> ---------------------------------------------------------------------------------------------
>
> Key: JBTM-2444
> URL: https://issues.jboss.org/browse/JBTM-2444
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Documentation
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Priority: Blocker
> Fix For: 5.next
>
>
> {code}
> Running org.jboss.narayana.quickstarts.jta.TestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 18.563 sec <<< FAILURE!
> Results :
> Tests in error:
> org.jboss.narayana.quickstarts.jta.TestCase: Cannot deploy: test.war
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> {code}
> The log file says:
> {code}
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /home/hudson/workspace/narayana-quickstarts/wildfly-10.0.0.Alpha4-SNAPSHOT/standalone/tmp/vfs/temp/temp174d29cf17a7dbea/content-a7b7e754b2627502/WEB-INF/test-jms.xml
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[23,1]
> Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment'"}}
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
> at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
> at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
> ... 96 more
> {code}
> Which leads me to believe it is likely due to the parsing in test-jms.xml.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (JBTM-2440) Disable byteman tests 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:
-------------------------------------
Do you know why these only seemed to start failing when we upgraded to JDK8?
> Disable byteman tests 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
> 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)
9 years, 5 months