3 Replies Latest reply on Nov 5, 2013 9:20 AM by Patrick Lightbody

    How does InVMCourier work?

    Patrick Lightbody Newbie

      Apologies, but I'm totally new to JBoss ESB. I'm an ex-Java open source guy though (OpenSymphony, Struts 2, etc), so hopefully I still can learn quickly Anyway, these days I do product management at New Relic and I'm helping a customer get better visibility in to their JBoss ESB app using our product. Our thread profiler indicates this partial stack trace as to where a bunch of time is being sent:


      35.0%  - org.jboss.soa.esb.client.ServiceInvoker.deliverSync

      35.0%  - org.jboss.soa.esb.client.ServiceInvoker.post

      35.0%  - org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200

      35.0%  - org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery

      35.0%  - org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup

      35.0%  - org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup

      35.0%  - org.jboss.internal.soa.esb.couriers.InVMCourier.pickup

      35.0%  - org.jboss.internal.soa.esb.couriers.transport.InVMTemporaryTransport.pickup

      35.0%  - org.jboss.internal.soa.esb.couriers.transport.InVMTemporaryTransport$InVMEntry.pickup

      35.0%  - java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await

      35.0%  - java.util.concurrent.locks.LockSupport.parkNanos

      35.0%  - sun.misc.Unsafe.park


      Without knowing the details of JBoss ESB or the customer's app, I'm guessing that what is happening here is the receiving service is inside the JVM (thus the name "InVMCourier") and there is not an actual HTTP POST taking place. Rather, some other thread is picking up the work and this profile simply shows off that 35% of the time we're waiting for that thread. What I can't figure out when browsing through the code is where that other thread pool is instantiated. It's important because this is where I'd like to add additional probes to find out the root cause of the slowdown. I've poked around ServiceInvoker, TwoWayCourierImpl, InVMCourier, InVMTemporaryTransport, etc but not seeing anything obvious like an ExecutorService.


      Any tips? Thanks!



      PS: If we can make some initial progress here, my hope is to use this work as the start of official JBoss ESB support for New Relic. Woot!