It looks like the issue with the consumer hanging has something to do with duplicate messages after a producer comes back from a failover.
I see the Producer reconnect after the network is restored. The broker receives a ActiveMQMapMessage. The ProducerBrokerExchange setting the last stored sequence id to -1. The AbstractStoreCursor store saying it received a duplicate message. After that the consumer stops receiving data the Queue keeps going up and the logs show the toPageIn going up for each message received. Thanks, Eric -- View this message in context: http://activemq.2283324.n4.nabble.com/Consumer-hanging-after-a-producer-fails-for-being-inactive-tp4689775p4689867.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
