Deployment of JBPM as a WAR/EAR in JBoss 7 – “rewards-jsf-6.0.1-SNAPSHOT.war” was rolled back with failure message Operation cancelled

While deploying the jbpm-examples-rewards-jsf application in JBoss AS 7.1.1 I faced the following problem:

18:48:11,776 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "rewards-jsf-6.0.1-SNAPSHOT.war" was rolled back with failure message Operation cancelled
18:48:11,776 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "jbpm-console.war" was rolled back with no failure message
18:48:11,776 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
18:48:11,796 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "dashboard-builder.war" was rolled back with no failure message
18:48:11,816 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016009: Stopping weld service for deployment dashboard-builder.war
18:48:11,816 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
18:48:11,826 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
18:48:11,826 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016009: Stopping weld service for deployment rewards-jsf-6.0.1-SNAPSHOT.war
18:48:11,836 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011403: Stopping Persistence Unit Service 'rewards-jsf-6.0.1-SNAPSHOT.war#org.jbpm.examples.rewards-jsf'
18:48:12,036 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment rewards-jsf-6.0.1-SNAPSHOT.war in 262ms
18:48:12,546 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment dashboard-builder.war in 738ms
18:48:31,362 INFO  [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

This problem means that the deployment is taking too long, so changing the timeout in file standalone.xml will solve the problem.

  <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
      <deployment-scanner path="deployments" 
                          relative-to="jboss.server.base.dir" 
                          scan-interval="5000" 
                          deployment-timeout="360"/>
  </subsystem>
Short URL for this post: http://wp.me/p4nxik-2iY
This entry was posted in Java EE, Java Runtimes - VM, Appserver & Cloud and tagged , . Bookmark the permalink.

Leave a Reply