Jboss 7 war deployment failed and i got the below error message in the log.
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
I tried restarting the JBoss server, I have never seen this before, it was working fine before. I googled around for solution and cause of this issue but cant find anything really useful, can anyone help please?
From the JBoss bin directory, run the command jboss-cli --connect to start the JBoss CLI and connect to the application server. Run the /deployment command on the compressed WAR file or exploded WAR folder. [If you are deploying to a managed domain, also run the /server-group command.]
We can create a dynamic web project in Eclipse, add a JBoss server and then configure the application to run on the server. Internally, Eclipse will create the war file of the application and place it in the JBoss directory. We can create an index. html file and set the welcome-file in web.
Yes, you can deploy two or multiple WAR files into EAP\standalone\deployments folder. Each web application will have a different context root, using context root you can access the application.
Well I tried deleting the log file, it helped at the beginning but then I got the error again. The proper solution is as following:
Go to Jboss_installation_dir\standalone\configuration
and find the file standalone.xml
. Change the following line:
<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.0"> <deployment-scanner scan-interval="5000" relative-to="jboss.server.base.dir" path="deployments" /> </subsystem>
into:
<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.0"> <deployment-scanner scan-interval="5000" relative-to="jboss.server.base.dir" path="deployments" deployment-timeout="1000" /> </subsystem>
then it should work fine.
NOTE: This deployment-timeout
is in seconds
It was caused by insufficient space on the disk, cleared some unwanted log files and other temp files to fix this issue.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With