[jboss-user] [JBoss Messaging] - Re: BisocketClientInvoker deadlock (Repost)
clebert.suconic@jboss.com
do-not-reply at jboss.com
Wed May 14 14:31:14 EDT 2008
Well... maybe this means the lock is not totally yours.
This thread is trying to acquire a writeLock:
"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)
| at java.lang.Object.wait(Object.java:474)
| at EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$WriterLock.acquire(WriterPreferenceReadWriteLock.java:240)
| - locked <0x47080570> (a EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$WriterLock)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.removeBindingInMemory(MessagingPostOffice.java:2280)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.internalRemoveBinding(MessagingPostOffice.java:1902)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.removeBinding(MessagingPostOffice.java:464)
| at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.close(ServerConnectionEndpoint.java:400)
| - locked <0x4b9a2598> (a java.util.HashSet)
| at org.jboss.jms.server.connectionmanager.SimpleConnectionManager.closeConsumersForClientVMID(SimpleConnectionManager.java:377)
| - locked <0x47196dc8> (a org.jboss.jms.server.connectionmanager.SimpleConnectionManager)
|
While this thread, holding a readLock is trying to connect back to the client:
"WorkManager(2)-10" daemon prio=10 tid=0x02d1e5a8 nid=0xc7 in Object.wait() [0xd6dea000..0xd6def8f0]
| at java.lang.Object.wait(Native Method)
| - waiting on <0xb94ac400> (a java.util.HashSet)
| at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:473)
| - locked <0xb94ac400> (a java.util.HashSet)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:801)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:551)
| at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:418)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
| at org.jboss.remoting.Client.invoke(Client.java:1634)
| at org.jboss.remoting.Client.invoke(Client.java:548)
| at org.jboss.remoting.Client.invokeOneway(Client.java:598)
| at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:826)
| at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:697)
| at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1432)
| at org.jboss.jms.server.endpoint.ServerSessionEndpoint.handleDelivery(ServerSessionEndpoint.java:1344)
| - locked <0x4ba02568> (a org.jboss.jms.server.endpoint.ServerSessionEndpoint)
| at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.handle(ServerConsumerEndpoint.java:322)
| - locked <0x4ba347f0> (a java.lang.Object)
| at org.jboss.messaging.core.impl.RoundRobinDistributor.handle(RoundRobinDistributor.java:119)
|
Do you think you could give it a try with the SVN:
svn co http://anonsvn.jboss.org/repos/messaging/branches/Branch_JBossMessaging_1_4_0_SP3_CP/ jbm
cd jbm
ant release-bundle
and let me know how it goes?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150855#4150855
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150855
More information about the jboss-user
mailing list