Apache and the Wildfly servers are enabled for http2.
At a customer site we observed that when Apache was under load it was routing requests to the incorrect Wildfly,
e.g. a request for the loga server went to the loga3 server or vice versa.
We were not able to reproduce this in the lab. For the customer the workaround was to disable http2 for both Wildflys.
Is this a known problem with Apache?
We are currently testing Apache 2.4.46, but as I said we were unable to reproduce the customer problem so we are reluctant to reactivate http2.
I would be grateful for any suggestions as to how to locate/solve this problem.