[John Spackman]

Hi,

My Tomcat project just slowed to an absolute crawl when debugging – the normal startup time for example is around 3000ms-4000ms, and it suddenly grew to 12,000ms-17,000ms, and the app seemed super slow when running. I tried lots of things to fix this, including uninstalling JSE6 and Tomcat 5.5.20 and reverting to JSE5, Tomcat 5.5.9, reconfiguring MyEclipse for the JREs and the Tomcat app server etc. If I started tomcat directly (without MyEclipse) startup was around 2,500ms and I found that running it from MyEclipse was only marginally slower. Debugging was still very sluggish.

Nothing fixed it, and I couldn’t find anything in the forums so I was about to reinstall MyEclipse when I tried deleting all the breakpoints and starting debugging again – that cured it. I think the problem might be that I was switching between two development trees (I close MyEclipse, rename directories, and restart – then refresh the project and redeploy) and it’s possible that some of the breakpoints pointed to a line of code or even an entire file which did not exist any more.

I don’t know if you already know about this, but I thought I’d mention it simply because I couldn’t find a solution when I searched the forums.

John

[Riyad Kalla]

John, we actually weren’t aware of a situation such as this. Thank you for sending this information along, we will look into this.

[steve hodge]

Hi,

I find this with my installation also. Any tips to find the cause of the delays?

Steve

[Riyad Kalla]

Steve,
Slow downs during debugging can be effected by:
1) Memory available, handled by start up arguments.
2) The number of projects open and source files that are “visible” to the debugger across all those projects. The more, the slower it will run.

[Author]

Posts