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

use a broker name based on the cr name in place of the default and hard coded name

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None

      The original Template model supported an AMQ_HOST env var that would specify the broker name. However once the operator started interacting with the broker jolokia endpoint, it used a hard coded broker name that did not respect the AMQ_HOST env var. Today setting the env var, breaks the operator/broker interactions. The hard coded name is of little value, but it does appear as a property in mbean names.

      If the default name was based on the CR name, there would be no good reason to change it as it would be sensible and meaningful.
      under the restrictedMode flag, we can fix this by using a more sensible default.

              gtully@redhat.com Gary Tully
              rh-messaging-ci Messaging CI
              Mikhail Krutov Mikhail Krutov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: