Yes,
It's clearly a deadlock...
Notice that the first thread is waiting to lock the same object that the
second thread has lockedmeanwhile, the second thread is not waking up,
it's "waiting for space".And the application grinds to a halt
In the first thread, see:
waiting to lock <0x
That stack trace looks more like a wait than a deadlock? Are you sure
its a real deadlock?
This FAQ entry should help
http://activemq.apache.org/my-producer-blocks.html
On 5/15/07, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
Hi all, I'm just using ActiveMQ for the first time. I've encountered
Hi all, I'm just using ActiveMQ for the first time. I've encountered a
deadlock condition, that appears rooted in the ActiveMQ internals. I'm not
sure if this is a known problem or not. I've been able to work around the
issue, but thought I'd forward this on, to see if it warrants filing a bug,
