This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
wildfly [2018/11/09 12:59] mstraub [HTTPS & TLS Certificate] |
wildfly [2020/05/26 16:40] mstraub Deployment Timeout |
||
---|---|---|---|
Line 102: | Line 102: | ||
</code> | </code> | ||
+ | |||
+ | ==== Deployment Timeout ==== | ||
+ | |||
+ | In case your deployments have a long setup time you must extend the default limit of 300 seconds. | ||
+ | |||
+ | Add these system properties to your ''/opt/wildfly/standalone/configuration/standalone.xml'' after the initial modules section (the timeout value is in seconds): | ||
+ | |||
+ | <code xml> | ||
+ | <system-properties> | ||
+ | <property name="jboss.as.management.blocking.timeout" value="900"/> | ||
+ | </system-properties> | ||
+ | </code> | ||
+ | |||
+ | Also add the timeout to the deployment-scanner: | ||
+ | |||
+ | <code xml> | ||
+ | <profile> | ||
+ | <subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0"> | ||
+ | <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" | ||
+ | scan-interval="5000" deployment-timeout="900" | ||
+ | runtime-failure-causes-rollback= | ||
+ | "${jboss.deployment.scanner.rollback.on.failure:false}"/> | ||
+ | </subsystem> | ||
+ | ... | ||
+ | </profile> | ||
+ | </code> | ||
==== Enabling GZIP Compression ==== | ==== Enabling GZIP Compression ==== |