This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
wildfly [2020/07/23 12:00] mstraub [Deployment Timeout] |
wildfly [2020/10/29 14:13] mstraub [Timeouts] |
||
---|---|---|---|
Line 16: | Line 16: | ||
sudo chown --no-dereference wildfly:wildfly /opt/wildfly | sudo chown --no-dereference wildfly:wildfly /opt/wildfly | ||
sudo chown -HR wildfly:wildfly /opt/wildfly | sudo chown -HR wildfly:wildfly /opt/wildfly | ||
+ | </code> | ||
+ | |||
+ | Create a management user | ||
+ | <code bash> | ||
+ | sudo -u wildfly /opt/wildfly/bin/add-user.sh | ||
</code> | </code> | ||
Line 22: | Line 27: | ||
sudo -u wildfly /opt/wildfly/bin/standalone.sh | sudo -u wildfly /opt/wildfly/bin/standalone.sh | ||
</code> | </code> | ||
+ | |||
+ | Visit the managment console: https://localhost:9990 | ||
Line 75: | Line 82: | ||
- | ==== Deployment Timeout ==== | + | ==== Timeouts ==== |
In case your deployments have a long setup time you must extend the default limit of 300 seconds. | In case your deployments have a long setup time you must extend the default limit of 300 seconds. | ||
Line 101: | Line 108: | ||
runtime-failure-causes-rollback= | runtime-failure-causes-rollback= | ||
"${jboss.deployment.scanner.rollback.on.failure:false}"/> | "${jboss.deployment.scanner.rollback.on.failure:false}"/> | ||
+ | </subsystem> | ||
+ | ... | ||
+ | </profile> | ||
+ | </code> | ||
+ | |||
+ | And to allow long transactions (if your logs contain tasks cancelled by the TransactionReaper) configure the default-timeout of the transaction subsystem: | ||
+ | |||
+ | <code xml> | ||
+ | <profile> | ||
+ | <subsystem xmlns="urn:jboss:domain:transactions:5.0"> | ||
+ | <core-environment node-identifier="${jboss.tx.node.id:1}"> | ||
+ | <process-id> | ||
+ | <uuid/> | ||
+ | </process-id> | ||
+ | </core-environment> | ||
+ | <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/> | ||
+ | <coordinator-environment default-timeout="900" statistics-enabled="${wildfly.transactions.statistics-enabled:${wildfly.statistics-enabled:false}}"/> | ||
+ | <object-store path="tx-object-store" relative-to="jboss.server.data.dir"/> | ||
</subsystem> | </subsystem> | ||
... | ... | ||
Line 187: | Line 212: | ||
When using HTTPS you should most probably also provide a valid [[https://de.wikipedia.org/wiki/Transport_Layer_Security|TLS]] (aka SSL) certificate. Otherwise browsers tend to block access to your page or at least give a big warning that the page is not secure. | When using HTTPS you should most probably also provide a valid [[https://de.wikipedia.org/wiki/Transport_Layer_Security|TLS]] (aka SSL) certificate. Otherwise browsers tend to block access to your page or at least give a big warning that the page is not secure. | ||
+ | |||
+ | FIXME explore: there seems to be a new way to configure Letsencrypt directly via the WildFly CLI since WildFly 14: https://developer.jboss.org/people/fjuma/blog/2018/08/31/obtaining-certificates-from-lets-encrypt-using-the-wildfly-cli | ||
The certificate must be present in a Java Keystore file. Copy ''com.example.jks'' to ''/opt/wildfly/standalone/configuration''. | The certificate must be present in a Java Keystore file. Copy ''com.example.jks'' to ''/opt/wildfly/standalone/configuration''. |