Running Tomcat through eclipse works fine in non-debug mode, but not in debug mode. When I try to start the Tomcat server in debug mode, the console output looks fine for a
I too stumbled upon this issue.
I closed all the irrelevant projects. Cleared out my breakpoints. Increased STS VM memory. Follow this blog: http://searchforsolutions.wordpress.com/2011/12/01/eclipse-jvm-settings-for-optimized-performance/ Disabled the JBoss tool validators and all other validators.
Now STS works like a charm!
Change default logging level from:
<root>
<level value="DEBUG" />
<appender-ref ref="ConsoleAppender" />
</root>
To :
<root>
<level value="OFF" />
<appender-ref ref="ConsoleAppender" />
</root>
I've gotten through the issue! Once I figured it out, I remember that this has happened before. I cleared all my breakpoints and it works fine. I have no idea why that would cause the outcome that is does, but it works.
I had this same problem in Galileo. Fast run but crawling debug. Thanks to the posts above, I cleared all the breakpoints and restarted Tomcat. That magically fixed the problem. fyi - I had 2 method breakpoints and other line breakpoints earlier. I did the tests to confirm the above theory about method breakpoints slowing down. Here's what I found. Looks like it's not the method breakpoint which is the problem, the problem was the method breakpoint which was still showing up in the breakpoints list in debug view, but was not existing in the code. I mean I changed the parameters of that method but the old breakpoint with older parameters was still existing in the breakpoint list. That was the culprit, when I removed that, the other method breakpoints did not slow down the server. So looks like eclipse was trying to search for something non-existing which seems to have slowed it down. Hope this helps.
I just ran into this problem myself, and this solution helped me out. However - I only had 1 breakpoint, rather than the 20+ of other posters. My one breakpoint, however, was a method breakpoint and not a line breakpoint - I wonder if the multitude of method calls at tomcat startup combined with the method breakpoint could be causing this problem... I just tried a small experiment:
I'm guessing this is the problem.