activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: Problem With Remote Debug OF Message Broker
Date Tue, 13 Sep 2016 15:31:08 GMT
I would expect start() to be called when the broker starts (hence the name)
not when a client connects.  If you really want to debug that method, there
is an option you can set on the debug port that prevents the application
from running until a debugger attaches.  You can find nore details via

I'd recommend figuring out what part of the code you think the problem is
in, and set the breakpoint there.  Don't try to step through the entire
codebase looking for the problem; it'll take too long.  And be forewarned
that pausing some of the code becomes a race against time because there are
timeouts on some code paths, and if you take too long it'll time out and
the behavior may change.


On Sep 13, 2016 7:41 AM, <> wrote:

I have been assigned to track down a problem that requires debugging of the
message broker.

For this particular situation we are running version 5.5.1 of ActiveMQ.

I downloaded the source code for version 5.5.1 of ActiveMQ and imported it
into an Eclipse project I created for this purpose.  I then created a
remote debugging configuration.  I set a breakpoint on the first line of
code in the start() function of ActiveMQConnection.  I then start my
message broker, start my Eclipse debug configuration and then start a JMS
client app (i.e. message consumer).  I can see from the messages I display
in my client (consumer) app that it makes a connection to the message
broker, but the breakpoint is never hit in my Eclipse debug session.

I selected the start() function because it was the function I was most sure
would be called by simply connecting to the message broker from a client.

Is there something I’m doing wrong to try to walk through the message
broker code?  Should I be setting breakpoints in different classes?

As an additional piece of information for anyone who decides to help with
this I am attaching a screen shot of my Eclipse debugger taken well after
my JMS client has connected to the message broker.  As you will see, the
tab in Eclipse that usually displays the source code is empty.

Thanks in advance for helping with this.


*Michael Tarullo*

Contractor (Engility Corp)

Software Engineer

FAA WJH Technical Center


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message