When you deploy a ear or war file in the JBoss AS 7, you might see “JBAS015877: Stopped deployment” error message in the log file, with a failed deployment.
For example, when I tried to deploy “MyProject.ear” file to JBoss AS 7, I see the following error message in the Jboss server.log file.
Also, in the deployment directory, I saw two files. My original ear file, and a .failed ear file. This also indicates that the deployment failed.
# cd /home/jboss-as-7.1.1.Final/standalone/log/ # tail server.log "18:03:13,759 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015877: Stopped deployment CONNECT-JB7-4.2.0.ear in 17822ms" # cd /home/jboss-as-7.1.1.Final/standalone/deployments/ # ls -altr -rw-r--r-- 1 root root 52578830 Jan 26 18:56 MyProject.ear -rw-r--r-- 1 root root 219 Jan 26 18:57 MyProject.ear.failed
My ear file is big, and it typically take a while to deploy it.
In JBoss 7, the default time-out for deployment is 60 seconds.
So, to fix this issue, you need to increase the default deployment time-out accordingly.
Add “deployment-time” parameter to the “deployment-scanner” in the standalone.xml file.
In the standalone.xml file, you’ll see the following line.
# cd /home//jboss-as-7.1.1.Final/standalone/configuration/ # vi standalone.xml <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/>
Append deployment-timeout=”3600″ to the above line at the end as shown below.
In this example, I’ve added a deployment-timeout of 60 minutes (60×60 seconds = 3600 seconds). Change this value depending on your requirement.
# vi standalone.xml <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" deployment-timeout="3600"/>