[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Something up with the in vm transport

[timfox]

When I run in vm tests on TRUNK I notice a typical stack trace to a server method looks something like this:


  |        at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(ServerSessionEndpoint.java:397)
  |         at org.jboss.jms.server.endpoint.ServerSessionEndpoint$SessionAdvisedPacketHandler.handle(ServerSessionEndpoint.java:1803)
  |         at org.jboss.messaging.core.remoting.PacketDispatcher.dispatch(PacketDispatcher.java:93)
  |         at org.jboss.messaging.core.remoting.impl.invm.INVMSession$PacketDispatcherCallable.call(INVMSession.java:118)
  |         at org.jboss.messaging.core.remoting.impl.invm.INVMSession$PacketDispatcherCallable.call(INVMSession.java:103)
  |         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
  |         at java.util.concurrent.FutureTask.run(FutureTask.java:123)
  |         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
  |         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
  |         at java.lang.Thread.run(Thread.java:595)
  | 

So the INVM transport is being used, but I would expect to see the execution done on the same thread all the way from the client.

Any idea what this thread pool is doing?


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

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