Camel routes hang after failover back to priority broker

Added as a subtask as ENTMQ-664 as they may be related. I'm also using essentially the same test case.In this test case, I've changed my connection settings so my connection looks like:| <property name="brokerURL" value="failover:(ssl://10.0.1.9:51616,ssl://10.0.1.9:51617)?randomize=false&priorityBackup=true&jms.prefetchPolicy.queuePrefetch=1"/>|| |

I'm also using:| <from uri="amq:TA.CA.INFRA.TEST?preserveMessageQos=true&concurrentConsumers=10" />|When I kill the priority broker, my consumers move. When I restart the main broker, I see a several errors on both brokers 1 and 2[1]. When my consumers detect the priority broker is back they move over, but they stop consuming. The route is alive and there are messages on the queue.[1]| WARN | Async error occurred: javax.jms.JMSException: Unmatched acknowledge: MessageAck

{commandId = 22749, responseRequired = false, ackType = 2, consumerId = ID:bluebird.local-49538-1410807510375-1:1:26:2, firstMessageId = ID:bluebird.local-49329-1410806957862-15:1:1:1:36052, lastMessageId = ID:bluebird.local-49329-1410806957862-7:1:1:1:36125, destination = queue://TA.CA.INFRA.TEST, transactionId = TX:ID:bluebird.local-49538-1410807510375-1:1:5644, messageCount = 5, poisonCause = null}

; Could not find Message-ID ID:bluebird.local-49329-1410806957862-15:1:1:1:36052 in dispatched-list (start of ack)||javax.jms.JMSException: Unmatched acknowledge: MessageAck

{commandId = 22749, responseRequired = false, ackType = 2, consumerId = ID:bluebird.local-49538-1410807510375-1:1:26:2, firstMessageId = ID:bluebird.local-49329-1410806957862-15:1:1:1:36052, lastMessageId = ID:bluebird.local-49329-1410806957862-7:1:1:1:36125, destination = queue://TA.CA.INFRA.TEST, transactionId = TX:ID:bluebird.local-49538-1410807510375-1:1:5644, messageCount = 5, poisonCause = null}

; Could not find Message-ID ID:bluebird.local-49329-1410806957862-15:1:1:1:36052 in dispatched-list (start of ack)|