3 Replies Latest reply on Jan 15, 2020 7:43 AM by marcwijma

    Wildfly 14.1 stops listening on http port




      We have deployed Wildfly 14.1 in domain mode as two node cluster in Active-Active mode on two different VMs running on CentOS 7.6.


      For both nodes http port is configured as 8099, https port as 8993. It was running properly but for last 2 weeks, we noticed that it stops listening on 8099 port randomly while the services are still up. We are able to access the application on https port and even access the management console. But there is no Wildfly process running on 8099 (http).


      In server.log, there is no indication of anything going wrong. OS logs also we checked, could not find what has killed the process. There is no hs_err_pi log file generated by Wildfly either.


      When running below command, we see no other process running on 8099 port.


      netstat -lntp | grep '8099'


      Any idea what could be causing this? Please let us know what logs are needed for this. Server Details are mentioned below:


      1) VM: CentOS Linux release 7.6.1810 (Core)

      2) Wildfly Version: 14.1

      3) domain.xml content


      <socket-binding-group name="standard-sockets" default-interface="public">

                  <socket-binding name="ajp" port="${jboss.ajp.port:8098}"/>

                  <socket-binding name="http" port="${jboss.http.port:8099}"/>

                  <socket-binding name="https" port="${jboss.https.port:8993}"/>

                  <socket-binding name="txn-recovery-environment" port="4712"/>

                  <socket-binding name="txn-status-manager" port="4713"/>

                  <outbound-socket-binding name="mail-smtp">

                      <remote-destination host="localhost" port="25"/>