Issue descriptionThis issue was discovered when trying to deploy TIBCO JasperReports Server 6.3.0 under WildFly 8.1.0.Final and Java 8. When trying to start WildFly the application wont deploy, and the following error trace can be found in the logs: | [toc] |
2016-08-08 14:02:19,800 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) () MSC000001: Failed to start service jboss.deployment.unit."jasperserver-pro.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jasperserver-pro.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "jasperserver-pro.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.1.0.Final.jar:8.1.0.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_101] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_101] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_101] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011666: Could not parse file /usr/local/wildfly-8.1.0.Final/standalone/deployments/jasperserver-pro.war/WEB-INF/applicationContext-jms.xml at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:99) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.1.0.Final.jar:8.1.0.Final] ... 5 more Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011666: Could not parse file /usr/local/wildfly-8.1.0.Final/standalone/deployments/jasperserver-pro.war/WEB-INF/applicationContext-jms.xml at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:96) ... 6 more Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] Message: Unexpected element '{http://www.springframework.org/schema/beans}beans' at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:90) ... 6 more
Cause
This error message is somewhat rare, and it is related specifically to JMS listener on specific versions of JBoss and Spring. Here are some related threads on this issue if you want look into more details on this:
- http://stackoverflow.com/questions/15367623/jboss-7-could-not-parse-file-meta-inf-hornetq-jms-xml
- https://developer.jboss.org/thread/198358?tstart=0
- https://developer.jboss.org/thread/222475
Resolution
One of the simplest solutions is to rename the /WEB-INF/applicationContext-jms.xml file so that it doesn't end with "-jms.xml", because that is what JBoss attempts to parse. Use the following steps:
stop JBoss WIldFly
rename the applicationContext-jms.xml file so that it doesn't end with "-jms.xml"
clear WildFly cache
restart the application server
Ref. case #00070541
Recommended Comments
There are no comments to display.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now