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

Configuring Clustered Broker Acceptor with SSL Generates Connector Configuration without sslEnabled=true on Openshift

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Undefined Undefined
    • None
    • AMQ 7.11.1.OPR.1.GA
    • operator
    • None
    • False
    • None
    • False
    • Documentation (Ref Guide, User Guide, etc.)
    • Important

      When configuring a broker in OpenShift via the web form, if SSL is enabled on the acceptor, the matching auto-generated Connector configuration does not have sslEnabled=true set, resulting in repeated cluster warnings in the logs.

      Generated Acceptor:

      <acceptor name="artemis">tcp://ex-aao-ss-1.ex-aao-hdls-svc.amq.svc.cluster.local:61616?protocols=CORE,AMQP,OPENWIRE,MQTT;sslEnabled=true;keyStorePath=/etc/ex-aao-tls-secret-volume/broker.ks;keyStorePassword=changepass;trustStorePath=/etc/ex-aao-tls-secret-volume/client.ts;trustStorePassword=changepass;tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;useEpoll=true;amqpCredits=1000;amqpMinCredits=300</acceptor>

      Generated Connector:

      <connector name="artemis">tcp://ex-aao-ss-1.ex-aao-hdls-svc.amq.svc.cluster.local:61616</connector>

              dbruscin Domenico Francesco Bruscino
              rhn-support-dhawkins Duane Hawkins
              Mikhail Krutov Mikhail Krutov
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: