We've come across a deadlock in our internal testing of HornetQ_2.2.11 (embedded in JBoss AS 7.1.0.Final). I've attached a jstack of the broker (see the very end where jstack prints out the deadlocked threads, a snippet of which I've printed below). I've also attached the broker boot & run-time logs. I couldn't find any mention of a similar issue on the forums or in JIRA. Should I (or one of you) create a JIRA defect for the issue?
Found one Java-level deadlock:
waiting to lock monitor 0x00002aaabc05d910 (object 0x00000007c69e5560, a org.jboss.remoting3.remote.InboundMessage),
which is held by "Remoting "uxesplxbld11" read-1"
"Remoting "uxesplxbld11" read-1":
waiting to lock monitor 0x00002aaab06223a8 (object 0x00000007c69e5580, a org.xnio.streams.BufferPipeInputStream),
which is held by "pool-5-thread-10"
Thanks for replying. FYI, I reposted the question above in the JBoss AS 7 forums here: https://community.jboss.org/thread/199071?tstart=0 . Just for my own interest, can you give me an idea why you think it is a jboss AS problem?