[dom]

Hi, sorry , I’ve been away, but the problem persists. The line the breakpoint is set on makes no difference but at the moment I have a breakpoint set on the following line:

if (user == null) {

I have a feeling it is a command setting on my tomcat start up but I can’t figure out what it might be.

Thanks again.

[Riyad Kalla]

dom,
Unfortunately I’m out of ideas… you *could* try doing a clean install of Tomcat 5.5, or just using the integrated Tomcat 6 server that ships with MyEclipse to make things easier during development.

[dom]

Hi – I have tried a clean install without any success. I have no debugging capability at all which is a real problem. I’m having to insert System.out.println statements in my code to read any values which is clearly no good. Are you able to tell me what a successful JVM launch configuration looks like in terms of arguments? I’m convinced it is the launch config that I have set up incorrectly. For example I have no optional JVM arguments currently (Window>Preferences>MyEclipse>Application Servers>Tomcat 5>JDK) – do I need any or should I have any? Similarly the launch config at (Window>Preferences>MyEclipse>Application Servers>Tomcat 5>Launch) In the Arguments tab I have for Program arguments only ‘start’ and VM arguments looks like this :

-Dcatalina.home=”C:/Program Files/Apache Software Foundation/Tomcat 5.5″ -Dcatalina.base=”C:/Program Files/Apache Software Foundation/Tomcat 5.5″ -Djava.endorsed.dirs=”C:/Program Files/Apache Software Foundation/Tomcat 5.5/common/endorsed” -Djava.io.tmpdir=”C:/Program Files/Apache Software Foundation/Tomcat 5.5/temp” -Djava.library.path=”C:/Program Files/Java/jdk1.6.0_02/bin;C:/Program Files/Apache Software Foundation/Tomcat 5.5/bin” -Dsun.io.useCanonCaches=false

If you could confirm my arguments are all correct (and I suspect they are not) at least I can eliminate that theory.

Many Thanks.

[Riyad Kalla]

dom,
The Launch Configurations are only necessary if you need multiple configurations of the same server or have a very custom need for starting the app server.

The normal mode of operation, for Tomcat especially is literally:

1. Go to Window > Prefs > MyEclipse > App Servers > Tomcat > Tomcat 5
2. Set the Home Dir
3. Go to the “JDK” sub-preference node under it, and set a JDK to launch Tomcat with

DONE!

Then you just deploy your app to Tomcat using MyEclipse, and start it from the servers view or toolbar but MAKE SURE you are starting it in Debug mode. NOTE this is under the “Launch” settings under Tomcat 5, make sure it’s set to debug.

Also if you are using the Servers view, you need to click the bug “Debug” button to launch the server, not the “Run” button.

[dom]

Hey – that last line solves it !! – I’ve been using the ‘run ‘ button – not debug. I thought that the fact the server was set to start in debug mode in the launch configuration was enough – indeed it does swicth to debug perspective on start up even when the run button is used but i guess the run button overrides the debugging when the server is started in this way. It’s kind of obvious now – with hindsight but that’s a v strange problem fixed. Thanks a million for all your help !!!

[Riyad Kalla]

Hey – that last line solves it !! – I’ve been using the ‘run ‘ button – not debug.

I did that too once when the Server view was new, and filed a bug that debugging wasn’t working… doh! 🙂

I think we could improve the usability of this a bit though, I’ll file an issue for us to look into it.

[raschin23]

Hello, I have the same problem, after a while MyEclipse stopped to recognize my breakpoints.
I have already tried everything, restarting with -clean option, changing to internal tomcat…
Please help!

[raschin23]

After reinstalling on different computers and weird stuff like that, I found out that there was just a simple Javascript error in my JSP page which caused tomcat to crash somewhere. After removing this bug debugging worked fine again…

[support-joy]

Good to hear that you are all set.

[Author]

Posts