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 James.Strachan wrote: > > Whoah, that looks like a bug in Derby to me. I wonder if its worth us > upgrading to a newer Derby release. We're on 10.1.1.0 whereas it looks > like Derby has released 10.2.1.6. > > I wonder can you reproduce with a newer Derby jar? > -- View this message in context: http://www.nabble.com/Consumer-deadlock--tf2635867.html#a7358200 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
