This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
wildfly [2018/08/23 14:42] mstraub |
wildfly [2020/07/23 11:44] mstraub |
||
---|---|---|---|
Line 40: | Line 40: | ||
</code> | </code> | ||
- | ==== System Service ==== | + | ==== systemd service ==== |
- | + | ||
- | === systemd === | + | |
- | + | ||
- | Since Ubuntu 15.04 systemd replaced upstart as default init system. | + | |
Create the file ''/etc/systemd/system/wildfly.service'' and adapt the IP to the IP the service is publicly accessible with: | Create the file ''/etc/systemd/system/wildfly.service'' and adapt the IP to the IP the service is publicly accessible with: | ||
Line 78: | Line 74: | ||
</code> | </code> | ||
- | === Upstart === | ||
- | Create ''/etc/init/wildfly.conf'' and adapt the IP to the IP the service is publicly accessible with: | + | ==== Deployment Timeout ==== |
- | <code> | + | |
- | start on (local-filesystems and net-device-up IFACE!=lo) | + | |
- | # stop on normal shutdown | + | In case your deployments have a long setup time you must extend the default limit of 300 seconds. |
- | stop on runlevel [016] | + | |
- | # -b binds the IP for port 8080, -bmanagement for port 9990 | + | Add these system properties to your ''/opt/wildfly/standalone/configuration/standalone.xml'' after the initial modules section (the timeout value is in seconds): |
- | exec sudo -u wildfly /opt/wildfly/bin/standalone.sh -b 127.0.0.1 -bmanagement 127.0.0.1 | + | |
+ | <code xml> | ||
+ | <system-properties> | ||
+ | <property name="jboss.as.management.blocking.timeout" value="900"/> | ||
+ | </system-properties> | ||
</code> | </code> | ||
- | The log ''/var/log/upstart/wildfly.log'' even includes system outs, messages printed from JNI code or crash / segfault information. | + | Also add the timeout to the deployment-scanner: |
- | Optionally select a specific config, e.g. ''--server-config=standalone.xml'' or use port offset when running several instances of WildFly on one machine with ''-Djboss.socket.binding.port-offset=1'' | + | <code xml> |
- | + | <profile> | |
- | + | <subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0"> | |
- | Then start and stop WildFly with | + | <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" |
- | <code bash> | + | scan-interval="5000" deployment-timeout="900" |
- | sudo start wildfly | + | runtime-failure-causes-rollback= |
- | sudo stop wildfly | + | "${jboss.deployment.scanner.rollback.on.failure:false}"/> |
+ | </subsystem> | ||
+ | ... | ||
+ | </profile> | ||
</code> | </code> | ||
- | |||
==== Enabling GZIP Compression ==== | ==== Enabling GZIP Compression ==== | ||
Line 205: | Line 203: | ||
<https-listener name="default-ssl" socket-binding="https" security-realm="SslRealm" enable-http2="true"/> | <https-listener name="default-ssl" socket-binding="https" security-realm="SslRealm" enable-http2="true"/> | ||
</code> | </code> | ||
+ | |||
+ | See [[SSL/TSL Certificates]] for more details. | ||
Sources: http://reallifejava.com/configuring-ssl-in-wildfly-8, https://stackoverflow.com/questions/32008182/wildfly-9-http-to-https | Sources: http://reallifejava.com/configuring-ssl-in-wildfly-8, https://stackoverflow.com/questions/32008182/wildfly-9-http-to-https |