activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-638) no way to get broker-led replay of messages for messages ACK'd in a transaction after rollback
Date Thu, 15 Jun 2006 03:11:51 GMT
     [ https://issues.apache.org/activemq/browse/AMQ-638?page=all ]

Hiram Chirino updated AMQ-638:
------------------------------

    Fix Version: 4.2

Since this will require some thought to get right, and does not seem like it's critical feature
users are requesting.. I'm targeting this for thr 4.2... perhaps we will get to this by then.

> 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/activemq/browse/AMQ-638
>      Project: ActiveMQ
>         Type: Improvement

>   Components: Broker
>     Reporter: james strachan
>     Assignee: Hiram Chirino
>     Priority: Trivial
>      Fix For: 4.2

>
>
> 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:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message