]
Gytis Trikleris commented on JBTM-2444:
---------------------------------------
REAT-AT Bridge test with JMS fails now. It's because they haven't updated
standalone-rts.xml and standalone-xts.xml configurations to use ActiveMQ. I've checked
it locally and that is the issue.
Seems that they have planned backwards compatibility, but it's not yet implemented:
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.