-
Bug
-
Resolution: Done
-
Major
-
JBoss A-MQ 6.1
When prioritizedMessages=true using JDBC persistent adapter set on the broker; periodically messages are "trapped" on the queue and cannot be consumed. The symptoms:
- JMX queue size shows messages on the broker.
- Browsing the queue shows no messages.
- Messages are in the underlying DB.
- No message can be consumed from the queue.
-This behaviour only seems to occur when using the JDBC persistence store (kahadb does NOT demonstrate the issue)
Example config
~~~
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry queue=">" producerFlowControl="false" useCache="true" prioritizedMessages="true" expireMessagesPeriod="0" memoryLimit="1 mb"/>
</policyEntries>
</policyMap>
</destinationPolicy>
~~~
- relates to
-
ENTMQ-1144 [Priority Messages, JDBC store] priority messages seem to be slow when retrieved from store
- Closed