- This topic has 7 replies, 3 voices, and was last updated 20 years, 9 months ago by
.
-
Posts
-
– System Setup ——————————-
Microsoft Windows 2000
Eclipse version: 3.0.0
Eclipse build id: 200402122000
Fresh Eclipse install (y/n): Y
If not, was it upgraded to its current version using the update manager? N
Other installed external plugins:
Lomboz – com.objectlearn.jdt.j2ee
RegEx – com.brosinski.eclipse.regex
CSS Editor – net.sourceforge.csseditor
JFaceDbc – net.sf.jfacedbc
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 3.7.0
Eclipse JDK version: 1.4.2_03-b02
Application Server JDK version: 1.4.2_03-b02
Are there any exceptions in the Eclipse log file? No– Message Body ——————————-
I have JBoss 3.2.3 configured to run with MyEclipse.
I set a breakpoint in a Struts Action.
I start the JBoss 3.2 Launcher in debug mode.
The Debug perspective is open.
I open a browser and select a link to initiate the Struts Action.
The Debugger in Eclipse takes over a minute to react and I can not do anything else in Eclipse.
After the breakpoint is visible in the Debug perspective I see a progress bar with the message:
JDI thread evaluations: JDI thread evaluations: 0% done
The percentage never changes from 0%.Since I can use the debugger thia way I have resorted to starting JBoss from it’s own bin directory in debug mode and attaching to it as a remote application.
Please help me find the slow performance problem with the launcher/debugging.
Thank you!
Eric
1.4.2_03-b02
This is most likely your problem. JDK 1.4.2 is notoriously buggy wrt the debug implementation. I’d suggest your run both Eclipse and the app server on JDK 1.4.1 to avoid such issues.
Eric,
I’ve been scouring this forums and the Eclipse newsgroups and can’t find what I think the problem might be: there is a setting in the debugger having to do with ‘Suspend execution’ of something, that REALLY makes performance absolutely terrible in some cases for people and isn’t necessary for a successful debugging session.I’m sorry I don’t have more details right now, as I mentioned I’m having a hard time finding any info on it.
Hi Scott,
I installed BEA WebLogic JRockit 1.4.1_05 and changed Eclipse and the MyEclipse launcher to use it.
It did speed up the startup time of Eclipse and JBoss.
I found that it did not improve the performance of the debugging of a breakpoint the first time it is incountered.
I found that after the first time hitting the breakpoint the performance is like using the Debugging a Remote Application.
I do have six projects open most of the time and several of them are very large source base. It could be the initial process of finding the source with the launcher that takes the performance hit the first time?
I hope this helps.
Eric
Eric,
I do have six projects open most of the time and several of them are very large source base. It could be the initial process of finding the source with the launcher that takes the performance hit the first time?
Actually, that could easily be it. When looking up source, each open project is a candidate for finding it since you can have any number of projects running within a server. The first time this is done, there will be a performance hit for a large number of open or highly populated projects. I believe you hit the nail right on the head with that analysis.
To test this hypothesis, can you try temporarily closing a couple of the large projects you’re not actively using? I would expect this to speed up debugging a good bit, if we’re correct.
That was it Scott!
I closed several large projects that were not needed for debugging and the performance was greatly improved.
Eric
