Older messages not consumed by the MDB while new ones are consumed
Issue
This issue was originally reported the day the application was first put in Production. The queue/A is durable. The behavior we saw is that 183 older messages were not being consumed. However, new messages sent to this queue by the only producer in the application were consumed and processed by the MDB. The producer was not blocked. The producer is a singleton service in our 2-node clustered environment. The configuration for address settings looks like this:
<address-settings>
<address-setting match="#">
<dead-letter-address>jms.queue.DLQ</dead-letter-address>
<expiry-address>jms.queue.ExpiryQueue</expiry-address>
<redelivery-delay>5000</redelivery-delay>
<max-size-bytes>10485760</max-size-bytes>
<address-full-policy>BLOCK</address-full-policy>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
</address-setting>
</address-settings>
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 6.0.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
