JBoss console reports "...Stopped deployment appeonserver.jar..." error

The JBoss server console reports the "...Stopped deployment appeonserver.jar..." error (see figure below) during the startup process.

Figure 72. Terminal


Cause A: There is not enough space left on the hard drive. Usually this will be explicitly indicated by the following message in the log file:

Caused by: java.io.IOException: No space left on device

Solution A: Stop JBoss server. Clean up the temporary files under JBoss server (typically, %JBOSS_HOME%\standalone\tmp) or clean up the hard drive to get more available space.

Cause B: The deployment has timed out. Usually you will see the following message in the log file:

"Did not receive a response to the deployment operation within the allowed timeout 
period [60 seconds]. 
Check the server configurationfile and the server logs to find more about the 
status of the deployment."

Solution B: Increase the timeout value for deployment in WildFly or JBoss EAP by the following steps:

Step 1: Open the %JBOSS_HOME%\standalone\configuration\standalone.xml file in a text editor.

Step 2: Locate and modify the "deployment-timeout" setting under the "subsystem" element. The default value is 60 seconds.

<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.0">
            <deployment-scanner name="default" path="deployments" 
scan-enabled="true" scan-
interval="5000" relative-to="jboss.server.base.dir" deployment-timeout="600"/>