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/16 20:47:25 UTC
[jira] Created: (AMQ-638) no way to get broker-led replay of
messages for messages ACK'd in a transaction after rollback
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: Bug
Components: Broker
Reporter: james strachan
Assigned to: 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
[jira] Updated: (AMQ-638) no way to get broker-led replay of
messages for messages ACK'd in a transaction after rollback
Posted by "james strachan (JIRA)" <ji...@activemq.org>.
[ 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
[jira] Commented: (AMQ-638) no way to get broker-led replay of
messages for messages ACK'd in a transaction after rollback
Posted by "james strachan (JIRA)" <ji...@activemq.org>.
[ http://jira.activemq.org/jira//browse/AMQ-638?page=comments#action_35768 ]
james strachan commented on AMQ-638:
------------------------------------
BTW - the StompTest and ruby stomp test cases all work when the connection is closed on a rollback - so there's a simple workaround right now; on rolllback zap your connection, which is a bit hardcore :). So being able to keep subscriptions open but just rollback ACKs would be better.
> 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: Bug
> 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
[jira] Updated: (AMQ-638) no way to get broker-led replay of
messages for messages ACK'd in a transaction after rollback
Posted by "james strachan (JIRA)" <ji...@activemq.org>.
[ http://jira.activemq.org/jira//browse/AMQ-638?page=all ]
james strachan updated AMQ-638:
-------------------------------
Priority: Trivial (was: Major)
> 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
> Priority: Trivial
> 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
[jira] Updated: (AMQ-638) no way to get broker-led replay of
messages for messages ACK'd in a transaction after rollback
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (AMQ-638) no way to get broker-led replay of
messages for messages ACK'd in a transaction after rollback
Posted by "james strachan (JIRA)" <ji...@activemq.org>.
[ http://jira.activemq.org/jira//browse/AMQ-638?page=comments#action_35808 ]
james strachan commented on AMQ-638:
------------------------------------
BTW I patched the ruby client to perform client side redelivery, so its a non-issue now for ruby clients
> 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
[jira] Updated: (AMQ-638) no way to get broker-led replay of
messages for messages ACK'd in a transaction after rollback
Posted by "james strachan (JIRA)" <ji...@activemq.org>.
[ http://jira.activemq.org/jira//browse/AMQ-638?page=all ]
james strachan updated AMQ-638:
-------------------------------
Fix Version: (was: 4.0)
> 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
> Priority: Trivial
>
>
> 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