activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (AMQ-3519) Allow getJMSRedelivered flag to survive a restart
Date Fri, 30 Sep 2011 12:07:45 GMT


Gary Tully resolved AMQ-3519.

    Resolution: Fixed
      Assignee: Gary Tully

feature in

Requires two options to enable. A connection factory needs the transactedIndividualAck=true
attribute. This tells a consumer to send acks as messages are delivered. They accumulate on
the broker till the transaction completes. The default behavior is to provide a single batch
ack before the transaction completes, which does not allow the broker to distinguish between
delivery and transaction completion.

On the KahaDBPersistenceAdapter, rewriteOnRedelivery=true is required. This ensures that the
delivery count is persisted on a transaction rollback. If the message is again read from the
journal (after a restart), it will have the correct redelivery status. This makes the JMSRedelivredFlag
bullet proof.
> Allow getJMSRedelivered flag to survive a restart
> -------------------------------------------------
>                 Key: AMQ-3519
>                 URL:
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker, JMS client
>    Affects Versions: 5.5.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: jms, redelivery, reliable
>             Fix For: 5.6.0
> Jmsredelivery status is maintained by the activemq consumer and in memory by the broker
when a consumer closes. If the broker is restarted, the redelivery status is lost.
> The broker never rewrites a message so the modified property is lost.
> To make the redelivery flag reliable, it needs to be persisted.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message