Primary Comment: As we divulged the details of our scenario(s) and how product documentation did not cover them, RH support resources asked poignant questions to give themselves the appropriate context and were able to address with detailed responses each layer of the onion we were forced to work through.

What problem/issue/behavior are you having trouble with? What do you expect to see? JBoss EWS 2.1 httpd starts as expected but does not listen on the port 6666 that we configured in ssl.conf for modcluster - only on the default 443 port. We see errors in the JBoss console output for MODCLUSTER00042 stating that a connection to the apache server on port 6666 is refused. EWS and EAP both run on the same RHEL 7.6 box Where are you experiencing the behavior? What environment? In our STG environment When does the behavior occur? Frequency? Repeatedly? At certain times? Every time we start up httpd and domain.sh What information can you provide around timeframes and the business impact? This is pre-production however we are approaching the end of our schedule and we need to get clustering working so we can begin UAT.