I'm developing with MyEclipse 6.5 Blue Edition as usual today, but I'm running into a weird problem. In the MyEclipse environment, I used to start Tomcat in debug mode every time. In this way, whether I need debug or not, I can probably use debug. The strange thing is: when I start debugging in the MyEclipse environment as usual, accessing the webapp is actually very slow and very slow, not ordinary, but a hundred times slower than usual, and it took a long time to even refresh the homepage of my webapps. , to the extent that it seriously affects development .
Tried various measures to no avail. It was later found that,
① It's fine to start directly in the Tomcat environment (start.bat of bin directly under Tomcat). Later, I thought that this is equivalent to starting it in non-debug mode in the MyEclipse environment.
② This morning, MyEclipse was started in non-debug mode, and it was very fast, but it was very slow to access webapp in debug mode. In fact, the non-debug mode startup in the MyEclipse environment is equivalent to the startup method in ①. So the debug mode of the MyEclipse environment is not equivalent to directly starting Tomcat's start.bat? ? This is of course the case, not equivalent. The debug mode startup under MyEclipse requires stronger interaction between MyEclipse and Tomcat, because debug can detect your changes to Project files (except configuration files)
③ I used the keyword myeclipse tomcat debug slow in Google this morning and found a very meaningful post. Finally got it. . . . . .
| This problem may be caused by the interaction between eclipse and tomcat. When starting tomcat in debug mode, a file read error occurs, and eclipse automatically sets a breakpoint, which causes tomcat to fail to start normally. The solution is as follows: start tomcat in debug mode, open breakpoints veiw, right-click -> Remove all, restart tomcat and it will be OK |