Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-2444

jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Done
    • None
    • 5.2.0
    • Documentation
    • None

    Description

      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
      

      The log file says:

      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
      

      Which leads me to believe it is likely due to the parsing in test-jms.xml.

      Attachments

        Issue Links

          Activity

            People

              gtrikler@redhat.com Gytis Trikleris
              thjenkin@redhat.com Thomas Jenkinson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: