It seems, that the broblem was realated to consumer deadlock, which was mentioned in http://www.nabble.com/Consumer-Deadlock-tf2014492.html#a5536571
Increasing broker memory limit and applying limits to the queues, seems to solve the problem. Danielius Jurna wrote: > > We can only reproduce this on the production server while waiting for > couple of days :-) > But I wonder what "waiting to lock <0x0000002aa17df278> (a > org.apache.derby.impl.services.locks.SinglePool) " means? I cannot find > that object to be locked in any other thread. Is that possible? > > But interesting thing is that > -- View this message in context: http://www.nabble.com/Consumer-deadlock--tf2635867.html#a7439533 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
