#1173 new
Bruno Ribeiro da Silva

Play war doesn't deploy on Jboss AS 7.0.2

Reported by Bruno Ribeiro da Silva | October 20th, 2011 @ 01:29 PM

I'm trying to deploy the booking sample from play 1.2.3 to a jboss as 7.0.2 but it failed to deploy. It appears that something has changed on jboss as and play to stopped working. I tested on jboss as 7.0.0 and it worked fine, but since there's improvements and fixes in jboss as 7.0.2 I would like to see play working on the current version.

Framework version: 1.2.3
Platform you're using: RHEL 6.1, Jboss AS 7.0.2, JRE/JDK 1.6

Reproduction steps:

$ play war -o $JBOSS_HOME/standalone/deployments/booking.war

$ touch $JBOSS_HOME/standalone/deployments/booking.war.dodeploy

$ $JBOSS_HOME/bin/standalone.sh


Error log from jboss as:

11:24:04,065 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "booking.war"
11:24:07,211 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."booking.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."booking.war".PARSE: Failed to process phase PARSE of deployment "booking.war"

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.0.2.Final.jar:7.0.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_27]

Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to parse POJO xml ["/home/bruno/Development/Programs/jboss-as-web-7.0.2.Final/standalone/deployments/booking.war/WEB-INF/lib/netty-3.2.4.Final.jar/META-INF/jboss-beans.xml"]

at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:130)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptors(KernelDeploymentParsingProcessor.java:104)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.deploy(KernelDeploymentParsingProcessor.java:76)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.0.2.Final.jar:7.0.2.Final]
... 5 more

Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1]
Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'

at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:98) [staxmapper-1.0.0.Final.jar:1.0.0.Final]
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59) [staxmapper-1.0.0.Final.jar:1.0.0.Final]
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:123)
... 8 more

11:24:07,215 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "booking.war" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit."booking.war".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit."booking.war".PARSE: Failed to process phase PARSE of deployment "booking.war""}}
11:24:07,246 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) Stopped deployment booking.war in 30ms
11:24:07,248 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Failed services" => {"jboss.deployment.unit."booking.war".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit."booking.war".PARSE: Failed to process phase PARSE of deployment "booking.war""}}}}

Comments and changes to this ticket

  • Bruno Ribeiro da Silva

    Bruno Ribeiro da Silva October 20th, 2011 @ 05:24 PM

    I have a workaround, but it could be nice to see this fixed in future versions.

    After jboss tries to deploy, it decompressed the booking.war, so I removed:



    And did:

    $ touch $JBOSS_HOME/standalone/deployments/booking.war.dodeploy

    Startup jboss then this time the deploy worked fine!

  • opensas

    opensas October 23rd, 2011 @ 10:39 PM

    • Tag set to openshift deploy jboss

    I can confirm this issue, and also the workaround provided by Bruno

    I'm trying to deploy to openshift, which has a jboss 7.0.1 ZAP version, but the workaround doesn't seem to work...

    I asked at openshift forums, https://www.redhat.com/openshift/forums/express/error-trying-to-dep...

  • opensas

    opensas October 23rd, 2011 @ 10:40 PM

    • Tag changed from openshift deploy jboss to cloud, deploy, jboss, openshift

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

People watching this ticket