I saw it only after I posted my latest reply.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150881#4150881
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150881
___
jboss-use
I'll elaborate on the previous:
The "Notify Thread" locks other threads since it acquires the lock on
UserConnectionImpl. What we're worried about is why this thread "hangs" while
trying to send a message. When reproducing this phenomena, we've witnessed two
scenarios:
1) "Notify Thread" hangs
Full stack, part 4 and final
| "Thread-10" daemon prio=10 tid=0x02fb9a40 nid=0x43 in Object.wait()
[0xdb05f000..0xdb05faf0]
| at java.lang.Object.wait(Native Method)
| - waiting on <0x47ea3eb8> (a
com.arjuna.ats.arjuna.coordinator.TransactionReaper)
|
Full stack, part 3
| "Timer-8" daemon prio=10 tid=0x0238ff18 nid=0x93 in Object.wait()
[0xd6caf000..0xd6cafaf0]
| at java.lang.Object.wait(Native Method)
| - waiting on <0x47080570> (a
EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$WriterLock)
|
Full stack, part 2
| "Thread-87" prio=10 tid=0x023abb10 nid=0xc2 in Object.wait()
[0xfde8f000..0xfde8fb70]
| at java.lang.Object.wait(Native Method)
| - waiting on <0x472adf38> (a java.lang.Object)
| at java.lang.Object.wait(Object.java:474)
|
Full stack, part 1
| Full thread dump Java HotSpot(TM) Server VM (1.5.0_08-b03 mixed mode):
|
| "RMI TCP Connection(40)-64.103.124.101" daemon prio=10 tid=0x0270d9f0
nid=0xef runnable [0xd981f000..0xd981f8f0]
| at java.net.SocketInputStream.socketRead0(Native Method)
|
Similar to post
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051404#4051404, we
are facing a dead lock in the JMSServerInvocationHandler.
JBM version 1.3.0 GA
JBAS version 4.2.0 GA
Java 1.5.0_08
OS Sun sparc 5.10 on Sun-Fire-V490
This is the stack trace of the running tread:
Threa
