Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-8064

Exposing AMQ Broker Deployed on OpenShift via Ingress Configuration Fails

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • None
    • AMQ 7.11.0.GA
    • operator
    • Important

      When trying to expose AMQ Broker via creation of an Ingress, the ingress is successfully created, but it appears no underlying route is created to hook the ingress to the broker. Connecting to the exposed ingress hostname and port with a client results in timeouts waiting to obtain the cluster topology. Connecting to the ingress with an AMQP client results in a " AMQP SASL header mismatch value 48, expecting 41. In state: HEADER0" error message.

      So far attempts to expose the broker with plain connectors, ssl termination (edge) and ssl passthrough don't seem to be working.

              dbruscin Domenico Francesco Bruscino
              rhn-support-dhawkins Duane Hawkins
              Tiago Bueno Tiago Bueno
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: