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 [2020/05/26 16:40] mstraub Deployment Timeout |
wildfly [2020/07/23 12:10] mstraub [Installation] |
||
---|---|---|---|
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 40: | Line 47: | ||
</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 76: | Line 79: | ||
systemctl status wildfly | systemctl status wildfly | ||
journalctl -f -u wildfly # view log and follow it live | journalctl -f -u wildfly # view log and follow it live | ||
- | </code> | ||
- | |||
- | === Upstart === | ||
- | |||
- | Create ''/etc/init/wildfly.conf'' and adapt the IP to the IP the service is publicly accessible with: | ||
- | <code> | ||
- | start on (local-filesystems and net-device-up IFACE!=lo) | ||
- | |||
- | # stop on normal shutdown | ||
- | stop on runlevel [016] | ||
- | |||
- | # -b binds the IP for port 8080, -bmanagement for port 9990 | ||
- | exec sudo -u wildfly /opt/wildfly/bin/standalone.sh -b 127.0.0.1 -bmanagement 127.0.0.1 | ||
- | </code> | ||
- | |||
- | The log ''/var/log/upstart/wildfly.log'' even includes system outs, messages printed from JNI code or crash / segfault information. | ||
- | |||
- | 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'' | ||
- | |||
- | |||
- | Then start and stop WildFly with | ||
- | <code bash> | ||
- | sudo start wildfly | ||
- | sudo stop wildfly | ||
</code> | </code> | ||
Line 107: | Line 86: | ||
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. | ||
- | Add these system properties to your ''/opt/wildfly/standalone/configuration/standalone.xml'' after the initial modules section (the timeout value is in seconds): | + | Add these system properties to your ''/opt/wildfly/standalone/configuration/standalone.xml''. The system-properties are a child element of server and must come after the extensions section. The timeout value is in seconds: |
<code xml> | <code xml> | ||
- | <system-properties> | + | <server..> |
- | <property name="jboss.as.management.blocking.timeout" value="900"/> | + | <extensions> |
- | </system-properties> | + | ... |
+ | </extensions> | ||
+ | <system-properties> | ||
+ | <property name="jboss.as.management.blocking.timeout" value="900"/> | ||
+ | </system-properties> | ||
+ | ... | ||
</code> | </code> | ||