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

Allow users to define custom last value queue keys

    XMLWordPrintable

Details

    • AMQ Sprint 3219

    Description

      Required features to migrate from legacy Qpid brokers

      Defining custom last value queue keys (qpid.last_value_queue_key), on artemis its hardcoded currently
      https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_MRG/2/html/Messaging_Installation_and_Configuration_Guide/Declaring_a_Last_Value_Queue.html

      Currently, the LVQ keys is hardcoded as _AMQ_LVQ_NAME, and we want to

      <address name="foo.bar">
      <multicast>
      <queue name="orders1" last-value-key="stock-symbols" />
      </multicast>
      </address>

      Attachments

        Issue Links

          is cloned by

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-2589 Document: Allow users to define custom last value queue keys

          • 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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-1180 Last value queues do not work

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              rh-ee-ataylor Andy Taylor
              rhn-support-whui Roger Hui
              Mikhail Krutov Mikhail Krutov
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: