Hi

testing different persistence adapters I've found that the broker
stops handling messages when using kaha persistence. 
Attached is a thread dump, the test case is 
queue1->L1->queue2-L2
where N messages are submitted to queue1, and for every messages
processed by L1, M messages are sent to queue2.
It happens using both client ack and dups_ok.
It doesn't happen using jdbc persistence.

Is this anything known? Is kaha supposed to be production ready?

Thanks
Francesco
-- 
View this message in context: 
http://www.nabble.com/Kaha-persistence-hangs-tf3015789.html#a8374932
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to