Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-6215

priority message dispatch can be affected by jms browser or expiry processing paging messages in error

    Details

      Description

      Using a pull consumer it should be possible to always get the most recent high priority message. Even with a default page size, using lazy dispatch should pull in the correct number of messages from the cursor to satisfy each consumer.
      However periodic message expiry processing and queue browsing via jms or jmx will affect dispatch by pulling messages into the cursor.
      Using a small maxBrowsePageSize and maxExpirePageSize should suffice to ensure a window for dispatch but this currently fails because the limits are not enforced.
      Also, asyncDispatch treats a jms browser as a consumer w.r.t paging messages from the cursor, which has a similar side effect and thwarts lazyDispatch

        Attachments

          Activity

            People

            • Assignee:
              gtully Gary Tully
              Reporter:
              gtully Gary Tully
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: