[
https://issues.apache.org/jira/browse/AMQCPP-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643567#comment-14643567
]
ASF subversion and git services commented on AMQCPP-577:
--------------------------------------------------------
Commit 4822f75deb774db91cdb0db8207b5961aae430b1 in activemq-cpp's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-cpp.git;h=4822f75 ]
https://issues.apache.org/jira/browse/AMQCPP-552
https://issues.apache.org/jira/browse/AMQCPP-577
Port all current MessageConsumer fixes from Java client to CMS
> Transacted processing stops working correctly after failover
> ------------------------------------------------------------
>
> Key: AMQCPP-577
> URL: https://issues.apache.org/jira/browse/AMQCPP-577
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Affects Versions: 3.8.0, 3.8.1, 3.8.2, 3.8.3, 3.8.4
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 3.9.0
>
>
> When a C++ application with Failover transport in use consumes from a queue
> on a master-slave broker pair or a single broker instance, and consumption is
> in transactional batches, then when a failover occurs the application does
> not recover from the failover properly. Although the application reconnects
> to the surviving broker, and new consumers are established, message flow is
> erratic and more exceptions are thrown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)