On JBoss AS 7 and WildFly the default rule is that archived applications use the auto­deploy mode while exploded archives require manual deploy mode.So you can either

1) Disable automatic deployment of zipped applications by executing the following CLI command (will require to include a .dodeploy marker file to trigger deployment) :


2) Disable the deployment scanner by executing the following CLI command:

[standalone@localhost:9999 /] /subsystem=deployment-scanner/scanner=default:write-attribute(name=scan-enabled,value=false)

On JBoss AS 4/5/6 you can disable JBoss hot deployment's feature through the the conf/jboss-service.xml file. Find the following line:

<!-- A flag to disable the scans -->
<attribute name="ScanEnabled">true</attribute>

Simply change to false and hot deployment will be disabled.
If on the other hand you simply want to reduce scan polling time, look for a few lines before:

<!-- Frequency in milliseconds to rescan the URLs for changes -->
<attribute name="ScanPeriod">5000</attribute>

This will set the scan time (in milliseconds)


Related articles available on mastertheboss.com

How do I make sure my MBean is deployed after my EJB ?

  If your MBean is dependant on another resource, supposing cont

How do I change the default lib directory in an ear file?

  Supposing you have an Enterprise application which has been pa

How to let JBoss deploy an application after other apps?

  If you are running JBoss AS 7 or WildFly check the following t

How to deploy an application temporarly with JBoss ?

One way to do it, is using the jboss.system:service=MainDeployer

How to add a custom JBoss archive in an Ear ?

JBoss custom archives (like .sar or .har) are not recognized by t

JBoss deployment directory configuration

In this tutorial we are going to show how to provide an alternati