Gary Tully created AMQ-6215:
-------------------------------
Summary: priority message dispatch can be affected by jms browser
or expiry processing paging messages in error
Key: AMQ-6215
URL: https://issues.apache.org/jira/browse/AMQ-6215
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.13.0
Reporter: Gary Tully
Assignee: Gary Tully
Fix For: 5.14.0
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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
