Found one Java-level deadlock:
=
"ActiveMQ Transport: tcp:///157.168.160.190:4244":
waiting to lock monitor 0x00a691ec (object 0x11286820, a java.lang.Object
),
which is held by "pool-2-thread-54"
"pool-2-thread-54":
waiting to lock monitor 0x00a6930c (object 0
Could you post a stack trace?
On 4/2/07, Dennis Cheung <[EMAIL PROTECTED]> wrote:
Hi,
I have similar deadlock issue on MutexTransport.
The transport thread having deadlock with another thread which is doing the
Consumer.close()
Any one can give advise to me?
thanks
On 10/26/06, kristoffer <[E
Hi,
I have similar deadlock issue on MutexTransport.
The transport thread having deadlock with another thread which is doing the
Consumer.close()
Any one can give advise to me?
thanks
On 10/26/06, kristoffer <[EMAIL PROTECTED]> wrote:
Hi,
Im speculating here: is it because the persistent fl
