You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2014/06/24 16:48:24 UTC
[jira] [Closed] (AMQ-638) no way to get broker-led replay of
messages for messages ACK'd in a transaction after rollback
[ https://issues.apache.org/jira/browse/AMQ-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-638.
----------------------------
Resolution: Fixed
There are several STOMP clients that now handle client side redelivery. There is also a way to have Broker led redelivery now.
> no way to get broker-led replay of messages for messages ACK'd in a transaction after rollback
> ----------------------------------------------------------------------------------------------
>
> Key: AMQ-638
> URL: https://issues.apache.org/jira/browse/AMQ-638
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Reporter: james strachan
> Priority: Trivial
> Fix For: AGING_TO_DIE
>
>
> Currently in OpenWire the client is expected to replay messages ACK'd in a transaction and then rolled back - which in general is a much better idea as its simpler & faster & avoids common ordering problems.
> However for simple stomp clients, we should have an option to allow a Rollback to mean, redeliver all messages which were ACK'd in the transaction.
> I wonder should we add a flag to ConsumerInfo to indicate if brokerRedeliveryOnRollback is enabled? Then we can keep Stomp clients super simple.
--
This message was sent by Atlassian JIRA
(v6.2#6252)