[jboss-user] [Remoting] - Re: Client timeouts while waiting for response from server

tomerc do-not-reply at jboss.com
Wed Dec 20 11:09:19 EST 2006


After doing some further investigating i found out the problem,
turns out there is a deadlock in BlockedLinkedQueue (from Doug Lee concurrent pacakge) for more information you can check out :
http://altair.cs.oswego.edu/pipermail/concurrency-interest/2004-September/001037.html


Following a stack trace of two of the jboss remoting threads :

 Thread: SocketServerInvokerThread-10.184.76.155-172 : priority:5, demon:false, threadId:954, threadState:BLOCKED, threadLockName:org.jboss.util.threadpool.MinPooledExecutor at 9e264b
  |                EDU.oswego.cs.dl.util.concurrent.PooledExecutor.execute(PooledExecutor.java:875)               
  |  org.jboss.util.threadpool.BasicThreadPool.execute(BasicThreadPool.java:413)               
  |  org.jboss.util.threadpool.BasicThreadPool.runTaskWrapper(BasicThreadPool.java:192)              
  |  
  | org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:212)               
  | 
  | org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:206)                
  | 
  | org.jboss.remoting.ServerInvoker.handleOnewayInvocation(ServerInvoker.java:910)               
  | 
  | org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:788)               
  | 
  | org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)                
  | 
  | org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)              
  |  org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)               
  | 
  | org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
  | 
  | 
  |             Thread: SocketServerInvokerThread-10.184.76.155-6 : priority:5, demon:false, threadId:197, threadState:BLOCKED, threadLockName:java.lang.Object at 1749fb5
  |                 EDU.oswego.cs.dl.util.concurrent.BoundedLinkedQueue.offer(BoundedLinkedQueue.java:328)                
  | 
  | EDU.oswego.cs.dl.util.concurrent.PooledExecutor.execute(PooledExecutor.java:885)                
  | 
  | org.jboss.util.threadpool.BasicThreadPool.execute(BasicThreadPool.java:413)                
  | 
  | org.jboss.util.threadpool.BasicThreadPool.runTaskWrapper(BasicThreadPool.java:192)                
  | 
  | org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:212)                
  | 
  | org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:206)                
  | 
  | org.jboss.remoting.ServerInvoker.handleOnewayInvocation(ServerInvoker.java:910)                
  | 
  | org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:788)                
  | 
  | org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)                
  | 
  | org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)                
  | 
  | org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)                
  | 
  | org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
  | 
  | 

Is there anyway to tell jboss remoting to use a different queue ?


Thanks.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995334#3995334

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995334



More information about the jboss-user mailing list