You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2010/02/01 23:40:33 UTC

[jira] Created: (AMQ-2590) Transaction commit/rollback through failover should throw TransactionRolledBackException if recovery redelivery dispatches another consumer

Transaction commit/rollback through failover should throw TransactionRolledBackException if recovery redelivery dispatches another consumer
-------------------------------------------------------------------------------------------------------------------------------------------

                 Key: AMQ-2590
                 URL: https://issues.apache.org/activemq/browse/AMQ-2590
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMS client
    Affects Versions: 5.3.0
            Reporter: Gary Tully
            Assignee: Gary Tully
             Fix For: 5.4.0


Given an outstanding consumer transaction and failover transport recovery. On recovery, messages are redispatched by the broker once the connection, sessions and producers/consumers and transactions are replayed. Redispatch may not dispatch the same messages to the same consumers atm. In the case that a client transaction cannot be recreated it should fail with a TransactionRolledBackException. The failure indicates that the messages the session wants to ack have not again been redispatched so their receipt cannot be committed. The messages in question will have been redelivered to another consumer. 
Likewise in a rollback, in this case there is a warn message to the effect that the rolled back messages may not all be included in the rollback. It that they may not have been redispatched. The unordered redelivery semantics after a session rollback ensure that this error does not need to propagate up to the client.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AMQ-2590) Transaction commit/rollback through failover should throw TransactionRolledBackException if recovery redelivery dispatches to another consumer

Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-2590:
----------------------------

    Fix Version/s: 5.3.1
          Summary: Transaction commit/rollback through failover should throw TransactionRolledBackException if recovery redelivery dispatches to another consumer  (was: Transaction commit/rollback through failover should throw TransactionRolledBackException if recovery redelivery dispatches another consumer)

on 5.3.1 branch a r905437

> Transaction commit/rollback through failover should throw TransactionRolledBackException if recovery redelivery dispatches to another consumer
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2590
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2590
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.3.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.3.1, 5.4.0
>
>
> Given an outstanding consumer transaction and failover transport recovery. On recovery, messages are redispatched by the broker once the connection, sessions and producers/consumers and transactions are replayed. Redispatch may not dispatch the same messages to the same consumers atm. In the case that a client transaction cannot be recreated it should fail with a TransactionRolledBackException. The failure indicates that the messages the session wants to ack have not again been redispatched so their receipt cannot be committed. The messages in question will have been redelivered to another consumer. 
> Likewise in a rollback, in this case there is a warn message to the effect that the rolled back messages may not all be included in the rollback. It that they may not have been redispatched. The unordered redelivery semantics after a session rollback ensure that this error does not need to propagate up to the client.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (AMQ-2590) Transaction commit/rollback through failover should throw TransactionRolledBackException if recovery redelivery dispatches another consumer

Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-2590.
-----------------------------

    Resolution: Fixed

resolved in r905432


> Transaction commit/rollback through failover should throw TransactionRolledBackException if recovery redelivery dispatches another consumer
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2590
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2590
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.3.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.4.0
>
>
> Given an outstanding consumer transaction and failover transport recovery. On recovery, messages are redispatched by the broker once the connection, sessions and producers/consumers and transactions are replayed. Redispatch may not dispatch the same messages to the same consumers atm. In the case that a client transaction cannot be recreated it should fail with a TransactionRolledBackException. The failure indicates that the messages the session wants to ack have not again been redispatched so their receipt cannot be committed. The messages in question will have been redelivered to another consumer. 
> Likewise in a rollback, in this case there is a warn message to the effect that the rolled back messages may not all be included in the rollback. It that they may not have been redispatched. The unordered redelivery semantics after a session rollback ensure that this error does not need to propagate up to the client.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.