[
https://issues.apache.org/jira/browse/AMQ-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3380.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.6.0
When tested against trunk the test passes. Fixes between 5.4.2 and trunk seem
to have resolved the issue.
> 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
> Fix For: 5.6.0
>
> 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
