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

[AMQ7, config update] purge-on-no-consumers not showing correct value

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • None
    • AMQ 7.0.2.GA
    • None
    • None
    • Hide
      • Start the broker
      • add the following config 
         <address name="expiry_queue">
        <anycast>
          <queue name="expiry_queue" purge-on-no-consumers="true" />
        </anycast>
      </address>
      • the broker will redeploy the queues and the purge-on-no-consumers=true for queue "expiry_queue" when viewed in JMX (as expected)
      • restart the broker.
      • the purge-on-no-consumers=false for queue "expiry_queue" when viewed in JMX . The JMX view does NOT match the configuration file.
      Show
      Start the broker add the following config <address name= "expiry_queue" > <anycast> <queue name= "expiry_queue" purge-on-no-consumers= " true " /> </anycast> </address> the broker will redeploy the queues and the purge-on-no-consumers=true for queue "expiry_queue" when viewed in JMX (as expected) restart the broker. the purge-on-no-consumers=false for queue "expiry_queue" when viewed in JMX . The JMX view does NOT match the configuration file.
    • AMQ Broker 7.1 Sprint 2

    Description

      When setting purge-on-no-consumers=true in the config for a queue , the setting seems to be initial set to "true" when viewed on the broker webconsole or JMX. This is the case if the configuration is updated while the broker is running or before the broker is started.

      However when the broker is subsequently restarted the purge-on-no-consumers is set to false when viewed from the webconsole or JMX. So the JMX/webconsole view does not match the configuration file.

      On subsequent restarts the purge-on-no-consumers remains set as false.

      Captured in upstream issue https://issues.apache.org/jira/browse/ARTEMIS-1405

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-770 purge-on-no-consumers attribute cannot be changed at run-time

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          ARTEMIS-1405 Loading...

          Activity

            People

              rh-ee-ataylor Andy Taylor
              rhn-support-pfox Patrick Fox (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: