You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "james strachan (JIRA)" <ji...@activemq.org> on 2006/03/17 18:53:26 UTC

[jira] Updated: (AMQ-638) no way to get broker-led replay of messages for messages ACK'd in a transaction after rollback

     [ http://jira.activemq.org/jira//browse/AMQ-638?page=all ]

james strachan updated AMQ-638:
-------------------------------

    type: Improvement  (was: Bug)

> no way to get broker-led replay of messages for messages ACK'd in a transaction after rollback
> ----------------------------------------------------------------------------------------------
>
>          Key: AMQ-638
>          URL: http://jira.activemq.org/jira//browse/AMQ-638
>      Project: ActiveMQ
>         Type: Improvement

>   Components: Broker
>     Reporter: james strachan
>     Assignee: Hiram Chirino
>      Fix For: 4.0

>
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira