Wildfly 14.1 stops listening on http port

[priyam.srivastava]

Hi,

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"/>

            </outbound-socket-binding>

</socket-binding-group>

[jaikiran]

But there is no Wildfly process running on 8099 (http).

How are you verifying this?

[priyam.srivastava]

How are you verifying this?

By runnning the below command:

netstat -lntp | grep 8099

This return no result. But when I run the same command for https port (8993), I get the result. I have already mentioned in my original message, that application is accessible over https port but not http.

[marcwijma]

Any progress on this? We experience the same using wildfly thru keycloak 7.0.1. We have 2 nodes configured thru standalone-ha.xml listening on 8080 (ssl offloading with a loadbalancer in front). If you have more clue's or a way - to at least - detect the issue more specific. That would be very very helpfull.