JBoss A-MQ; Unexpected redelivery behaviour when using broker's redeliveryPlugin and consumer side redelivery mechanism together.

Solution Verified - Updated -

Issue

  • seeing the message redelivered to the consumer application code more times than expected when the broker's redeliveryPlugin and consumer redelivery mechanism configured. In detail:
    1. Client received a message and it was redelivered 6 times at default(1000ms) intervals (consumer's thread).
    2. Client sent POISON_ACK to broker when redeliveryCount reaches maximumRedeliveries.
    3. Broker increments redeliverCount after received POISON_ACK from the consumer, and the message is rescheduled delivery to the client[1].
    4. Client redelivered the message (6 - redeliverCount) times at default(1000ms) intervals (consumer's thread).
    5. Repeated from 2 to 4 until the broker's redeliverCount reaches maximumRedeliveries(=3). Then sent the message to DLQ.

Environment

  • JBoss A-MQ 6.0, ActiveMQ 5.8

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.