I have not reproduced the issue that I regionally experienced sadly. If I do, I will attempt to capture it in a unit test as you suggest.
Interesting pont about the short timeout; if we indeed need such a short timeout then persistence is pointless indeed. My requirements are atypical it seems: small message with a short shelf-like; if a broker goes down then ideally some mechanism kicks in quickly (i.e. in seconds, not minutes) to deliver the message. The speed of kahadb makes me hopeful that persistent messages will work for us; but the master/slave failover does not provide the lightning fast recovery that we want. Could a network of brokers help in this scenario? THANKS! -- View this message in context: http://activemq.2283324.n4.nabble.com/Runaway-producer-Proper-way-to-clean-up-a-topic-tp4677644p4677673.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
