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

Broker Scheduled messages requires better administration capabilities

    XMLWordPrintable

Details

    • Story
    • Resolution: Unresolved
    • Major
    • None
    • None
    • None
    • None
    • Documentation (Ref Guide, User Guide, etc.)

    Description

      The broker needs to be able to
      1. Report Total number of messages scheduled on the broker
      2. Report Total number of messages scheduled per destination (queue/topic)
      3. Way to purge scheduled messages based on destinations
      4. Way to inspect the scheduled messages (attributes, payload)
      5. Scheduler needs to work at scale.

      Attachments

        Issue Links

          duplicates

          Sub-task - The sub-task of the issue ENTMQBR-377 Broker Scheduled messages requires better administration capabilities

          • 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.
          • New
          is related to

          Sub-task - The sub-task of the issue ENTMQBR-377 Broker Scheduled messages requires better administration capabilities

          • 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.
          • New

          Activity

            People

              Unassigned Unassigned
              wdecoste1@redhat.com William Decoste (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: