Debugger not stopping at breakpoints: Websphere in Eclipse

Question

I've recently had my app moved from Websphere Application Server 6.1 to WAS 7.5, due to end-of-life for 6.1. Consequently, I needed to update my debugging server. I found this to be an opportune time to move my application from an IBM RAD IDE to Eclipse (already had Indigo installed). Or so I thought.

Anyway, the powers that be, here, have recommended taking my debugger all the way to WAS 8.5, since I'm only using it to debug.

But the issue that I'm encountering is that I cannot get the debugger to stop on my breakpoints. I've got approx. 10 breakpoints in my opening page, all in JSP/Java code.

I'm running Java 1.6.0_32 and Java SE Runtime Environment build 1.6.0_32-b05. I really don't know how to check which JDK I've got loaded. I've seen recommendations to "go back" to JDK 1.5, but I can't be certain that's not what I'm running.

And to cover a few other bases, I have JUST started my system for the day, opened the IDE, started the server in debug (says "Debugging, Synchronized"), put focus on the opening page of the application and clicked "Debug on server". The front page opens without stopping at any of the breakpoints.

Does anyone have ideas or suggestions?

Solution 1

If you use eclipse's debugger and running the application outside eclipse environment , we have to configure it as remote java application. Also check if the code deployed in server is in sync with the one present in workspace.

Solution 2

anything wrong of the ecplise's site.

Run->Skip all breakpoints

Solution 3

Well, I had recently faced this problem, where the code did not use to stop at breakpoints while I was in debugging mode and was sure that the particular piece of code is executing. In order to solve the problem, I did a clean-build-republish but it did not work, recreated the profile and readded the server with new profile, still did not work then finally re-installed RAD and web-sphere but It still did not work. Then I found the below article https://www-304.ibm.com/support/docview.wss?uid=swg21240896

and realized it could be a problem due to some other OS process interfering with debug process/port so I performed a system restore. After restore when I deployed the application, debugger started working properly.

Comments

[RAS]

I also face this kind of issue sometimes. But generally restarting the app, building the app, re-putting and re-enabling the breakpoints solve my problem.

[CoMo G-Dawg]

I have attempted the suggestion from RAS with no gain. At this point in time, I have gone back to using IBM RAD, with all of the cost and overhead, as it will actually function and allow me to debug my code. I am 2 weeks behind on this project and really need it done. Then I can go back to figuring out debugging in Eclipse with WAS.

[CoMo G-Dawg]

Well, I never did get this going. What I ended up doing was scrapping the local WAS debugger and got Jetty working, instead. Didn't answer this issue, but solved my problem.

[CoMo G-Dawg]

Have already checked the Skip All Breakpoints possibility. I have done some research on this and this was recommended as a possible solution on several other posts. I checked it before posting my question. Sorry that I didn't make that clear.

[CoMo G-Dawg]

The code is synched between IDE and server. As I had stated, I just restarted my system, my IDE and the debugger server. I don't know how others are configured, but my debugger refreshes the code on the server every time the server restarts. Also, I have manually restarted the server and manually published the files to the server.

[CoMo G-Dawg]

I will look into the possibility that this needs to be configured as a remote java application. I don't recall having to do that when I installed in RAD, but that doesn't mean it's not the case. Thanks for that suggestion!

[Suresh Anbarasan]

Also check if the IDE is in debug perspective.