[
https://issues.apache.org/jira/browse/AMQ-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-3519.
-----------------------------
Resolution: Fixed
Assignee: Gary Tully
feature in http://svn.apache.org/viewvc?rev=1177619&view=rev
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: https://issues.apache.org/jira/browse/AMQ-3519
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
