-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.ER2
-
None
Server Migration Tool - EAP 6.4 based *-jms.xml are not transferred to new format, server boots with errors.
Update: This is general "issue" with deployments which need to migrated, JBoss Server Migration Tool copies those artifacts without any modification
Eduardo suggests:
To prevent this kind of issue, I suggest the following changes on the tool's behaviour:
- when running in non interactive mode the configuration defaults to skip deployments migration
- when running in interactive mode the executed migration task first asks if deployments migration should be skipped, alerting that compatibility is not asserted. Currently it just asks if all deployments should be migrated, the alert regarding compatibility is only seen on the tool's user guide.
Details from boot failure:
15:20:26,960 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."xxx-jms.xml".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xxx-jms.xml".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "xxx-jms.xml" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172) [wildfly-server-3.0.0.Beta30-redhat-1.jar:3.0.0.Beta30-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /home/rsvoboda/TESTING/710ER3/jboss-eap-7.1/standalone/data/content/80/d6261a9e1bea0356f4a03fe3090b6dc43d12e4/content at org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165) [wildfly-server-3.0.0.Beta30-redhat-1.jar:3.0.0.Beta30-redhat-1] ... 5 more Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /home/rsvoboda/TESTING/710ER3/jboss-eap-7.1/standalone/data/content/80/d6261a9e1bea0356f4a03fe3090b6dc43d12e4/content at org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) ... 6 more Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment' at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:120) at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76) at org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) ... 6 more
My xxx-jms.xml copied into deployments directory of EAP 6.4.0 GA looks like this:
<?xml version="1.0" encoding="UTF-8"?> <messaging-deployment xmlns="urn:jboss:messaging-deployment:1.0"> <hornetq-server> <jms-destinations> <jms-queue name="sample"> <entry name="jms/queue/sample"/> <entry name="java:jboss/exported/jms/queue/sample"/> </jms-queue> </jms-destinations> </hornetq-server> </messaging-deployment>
Starting with WildFly 8 the structure of -jms.xml files changed a bit, look at 'Deployment of -jms.xml files' section of https://docs.jboss.org/author/display/WFLY/Messaging+configuration
- is blocked by
-
CMTOOL-143 Change default behaviour to skip deployments migration
-
- Closed
-
- is duplicated by
-
JBEAP-12388 Server Migration Tool - add 'none' option for 'Migrate all deployments?'
-
- Closed
-
- is incorporated by
-
-
- Closed
-
- is related to
-
WINDUPRULE-304 JMS Deployment Descriptors Changes in JBoss EAP 7
-
- Dev Complete
-
-
-
- Closed
-
