Dear all,
One of our Wildfly instances stopped abruptly to handle https requests. We checked and Wildfly is no longer listening in https port (8443).
Version: wildfly-14.0.1.Final
Oracle Linux Server release 7.6
standalone.xml
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
<socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
<socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>
<socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
<socket-binding name="http" port="${jboss.http.port:8080}"/>
<socket-binding name="https" port="${jboss.https.port:8443}"/>
$ netstat -an | grep 8843
$ lsof -p 4106 | grep https
java 4106 mmt mem REG 249,2 13048 16936336 /opt/seven/wildfly-14.0.1.Final/modules/system/layers/base/org/jboss/ws/jaxws-undertow-httpspi/main/jaxws-undertow-httpspi-1.0.1.Final.jar
java 4106 mmt 517r REG 249,2 13048 16936336 /opt/seven/wildfly-14.0.1.Final/modules/system/layers/base/org/jboss/ws/jaxws-undertow-httpspi/main/jaxws-undertow-httpspi-1.0.1.Final.jar
In other instance that is running properly with same setup:
$ netstat -an | grep 8443
$lsof -p 15350 | grep https
java 15350 mmt mem REG 249,2 13048 16973197 /opt/seven/wildfly-14.0.1.Final/modules/system/layers/base/org/jboss/ws/jaxws-undertow-httpspi/main/jaxws-undertow-httpspi-1.0.1.Final.jar
java 15350 mmt 417u IPv4 3743045405 0t0 TCP *:pcsync-https (LISTEN)
java 15350 mmt 520r REG 249,2 13048 16973197 /opt/seven/wildfly-14.0.1.Final/modules/system/layers/base/org/jboss/ws/jaxws-undertow-httpspi/main/jaxws-undertow-httpspi-1.0.1.Final.jar
What could be the root cause for this behaviour and how to avoid it?
Thanks in advance