You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Martin Serrano (JIRA)" <ji...@apache.org> on 2011/06/28 17:35:16 UTC

[jira] [Updated] (AMQ-3380) Exclusive consumers do not rollback session when switched after master slave failover

     [ https://issues.apache.org/jira/browse/AMQ-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Serrano updated AMQ-3380:
--------------------------------

    Attachment: master-slave-exclusive-consumer-test.patch

Patch which adds a unit test that demonstrates this behavior.  The test sends 100 messages.  After 25 messages are sent, the master is stopped.  The new consumer gets 75 messages.

> Exclusive consumers do not rollback session when switched after master slave failover
> -------------------------------------------------------------------------------------
>
>                 Key: AMQ-3380
>                 URL: https://issues.apache.org/jira/browse/AMQ-3380
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.2
>            Reporter: Martin Serrano
>            Priority: Critical
>         Attachments: master-slave-exclusive-consumer-test.patch
>
>
> This is a pure master/slave setup with multiple transacted exclusive consumers.  When the master is stopped, the exclusive consumer is switched (which seems odd to me).  This would be okay except the prior consumer is not rolled back.  The new consumer does not see all the messages (presumably since the prior consumer was not rolled back).  In rare cases in my environment, I have experienced message loss -- a message does not get sent on the new consumer.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira