Advertise with us

Our eBooks

How to configure JBoss to disable hot deployment ?

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) :

/subsystem=deployment-scanner/scanner=default:write-attribute(name=auto-deploy-zipped,value=false)

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)

© 2021 mastertheboss.com. All Rights Reserved.

Please publish modules in offcanvas position.