Eclipse Community Forums: Java Development Tools (JDT)

Home » Language IDEs » Java Development Tools (JDT) » Remote Debugging Problem(Remote Debugger not find source code in project)

Show: Today's Messages :: Show Polls :: Message Navigator

Remote Debugging Problem [message #1743153]

Mon, 12 September 2016 17:52

Mike Tarullo

Messages: 14
Registered: April 2010

Junior Member

I am trying to debug the Apache ActiveMQ message broker using remote debugging in Eclipse.

I have activated the debugger on the message broker side by commenting the specified line in the ActiveMQ startup script.

I have downloaded the source code for the version of ActiveMQ I am using and added it to an Eclipse project.

I have configured a remote debugging session in Eclipse.

I have set a breakpoint in the ActiveMQ Connection source code at the start() function, which I am certain is executed when I run my JMS client.

I start the message broker, start the remote debugger session in Eclipse and start my JMS client app.

I can see that my app makes a connection but the debug session nevers shows my breakpoint or the source code. I have attached a screen shot of what the debugger looks like at the point where I would expect to see the source code stopped at my break point.

Can you tell me what is wrong?

Thank you.

Attachment: MessageBrokerDebug1.png
(Size: 111.25KB, Downloaded 129 times)

Report message to a moderator

Re: Remote Debugging Problem [message #1743168 is a reply to message #1743153]

Mon, 12 September 2016 20:41

Stephan Herrmann

Messages: 1853
Registered: July 2009

Senior Member

Possibly the line number doesn't match the currently running version of the software?
You may want to try a method entry breakpoint instead, which is independent of line numbers.

Report message to a moderator

Re: Remote Debugging Problem [message #1743226 is a reply to message #1743168]

Tue, 13 September 2016 12:06

Mike Tarullo

Messages: 14
Registered: April 2010

Junior Member

Thank you Stephan!

I think it is more than just that.

In fact, for the source code I downloaded from the Apache web site and the version of Apache ActiveMQ I am attempting to debug, I did have this working somewhat in the past. I created a new project and re-imported the source code to try to correct some of the earlier problems I was having and that made things worse. As you can see from the screen image I uploaded, the tab in the IDE that should contain the source code is totally blank. In fact it does not even contain the usual message I have seen in the past when Eclipse can't find the source code.

Report message to a moderator

Re: Remote Debugging Problem [message #1743238 is a reply to message #1743226]

Tue, 13 September 2016 14:00

Stephan Herrmann

Messages: 1853
Registered: July 2009

Senior Member

The screenshot doesn't prove much, because we don't know why it should show any source code in the current state (i.e., no breakpoint has fired).

Have you tried the method entry breakpoint I mentioned?

Report message to a moderator

Re: Remote Debugging Problem [message #1743262 is a reply to message #1743238]

Tue, 13 September 2016 16:21

Mike Tarullo

Messages: 14
Registered: April 2010

Junior Member

No Stephan I have not done that yet because I'm not even sure at this point that the method I chose is a good place to start. I selected it because It appeared to me from looking at the ActiveMQ source code that it would be the method that gets called when I connect to the message broker from my client app.

So trying your approach, while I understand it's value, won't do anything if I'm that far off target trying to find a place to gain entry.

I have posted something on the ActiveMQ mailing list. From the first response I received it looks like I'm right about having placed the breakpoint in the wrong place, now I just need someone to tell me why the place I chose is not the right place, and more importantly, what is the correct place.

Report message to a moderator