A defect in a new feature delivered on the OpenShift 4.4 release line causes a regression for certain AMQP websocket use-cases. If an AMQ Interconnect listener is exposed using an OpenShift route with a TLS termination option 'reencrypt', attempted websocket connections will fail with the newer OpenShift versions. [A workaround is to use a different OpenShift Route TLS termination type (passthrough, edge)].

Whilst the defect here is with OpenShift, if AMQ Interconnect has the ability to turn off HTTP2 (a global flag would suffice - env var would be good enough), this would allow user, including AMQ Online to side step the OpenShift defect in the meanwhile.