JBoss Community

Re: SSL bisocket socketWrite0() hangs, while holding Messaging Post Office lock (on a network failure)

created by Todd Sandor in JBoss Remoting - View the full discussion

Ooops ...Forgot to specify, the lock is held here:

 

at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.routeInternal(MessagingPostOffice.java:3133)

 

Note sure whey the thread-dump does not display that it is holding this lock...?

 

 

Many/many other threads then waiting for this lock ...e.g;

 

2012.07.26 13:23:38 -0500 INFO  [STDOUT] "WorkerThread#122[10.217.178.53:3868]" Id=8486 WAITING on EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$ReaderLock@1956aca

    at java.lang.Object.wait(Native Method)

    -  waiting on EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$ReaderLock@1956aca

    at java.lang.Object.wait(Object.java:485)

    at EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$ReaderLock.acquire(WriterPreferenceReadWriteLock.java:163)

    at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.getBindingForQueueName(MessagingPostOffice.java:1033)

    at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.localClose(ServerConsumerEndpoint.java:568)

    at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.close(ServerConsumerEndpoint.java:414)

    at org.jboss.jms.server.endpoint.advised.ConsumerAdvised.org$jboss$jms$server$endpoint$advised$ConsumerAdvised$close$aop(ConsumerAdvised.java:59)

    at org.jboss.jms.server.endpoint.advised.ConsumerAdvised$close_N4742752445160157748.invokeTarget(ConsumerAdvised$close_N4742752445160157748.java)

    at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)

    at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)

    at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)

    at org.jboss.jms.server.endpoint.advised.ConsumerAdvised.close(ConsumerAdvised.java)

    at org.jboss.jms.wireformat.CloseRequest.serverInvoke(CloseRequest.java:66)

    at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:165)

    at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:967)

    at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:791)

    -  locked org.jboss.remoting.transport.socket.ServerThread@16b5e33

    at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:744)

    at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:586)

    at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234)

 

..

 

2012.07.26 13:23:38 -0500 INFO  [STDOUT] "WorkerThread#64[10.143.109.23:41474]" Id=1414 WAITING on EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$ReaderLock@1956aca

    at java.lang.Object.wait(Native Method)

    -  waiting on EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$ReaderLock@1956aca

    at java.lang.Object.wait(Object.java:485)

    at EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$ReaderLock.acquire(WriterPreferenceReadWriteLock.java:163)

    at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.getBindingForQueueName(MessagingPostOffice.java:1033)

...

 

2012.07.26 13:23:38 -0500 INFO  [STDOUT] "WorkerThread#122[10.217.178.53:3868]" Id=8486 WAITING on EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$ReaderLock@1956aca

    at java.lang.Object.wait(Native Method)

    -  waiting on EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$ReaderLock@1956aca

    at java.lang.Object.wait(Object.java:485)

    at EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$ReaderLock.acquire(WriterPreferenceReadWriteLock.java:163)

    at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.getBindingForQueueName(MessagingPostOffice.java:1033)

...

 

Cheers

Reply to this message by going to Community

Start a new discussion in JBoss Remoting at Community