Where to put breakpoints depends a little bit on your configuration (e.g. if you put a breakpoint in the FailoverTransport but you're not using failover, then of course you're not going to hit it), but you should be able to get a hit in just about any configuration if you set a breakpoint in TransportConnection.dispatchAsync() and the onCommand() method of the anonymous DefaultTransportListener created in TransportConnection's constructor.
Disclaimers: 1. I'm looking at 5.8.0 code right now, so you may need breakpoints in other places for other versions. 2. I'm not at a point where I can attach a debugger to confirm that the code actually hits those breakpoints, so I'm going from memory that those are valid places for a breakpoint. If they don't work, reply back with what you're seeing and we can go from there. 3. I think you're asking for how to debug the broker rather than the client, but I wasn't sure since you referenced "using the proton based client". On Thu, Mar 26, 2015 at 12:13 AM, Megala Uthayakumar <ktumeg...@gmail.com> wrote: > Hi all, > > I am trying to find out the path of a message which goes through the > activemq broker. I tried to do the remote debug using the proton based > client, the broker successfully connects to debug port. Client also > shows the expected behavior with the activemq broker. But no debug > points are hit during the execution. Could someone help on where I can > put the debug points so that I can find the message flow inside the > activemq broker. > > thank you. > > regards, > Megala >
