[J.C. Hamlin]

Using MyEclipse 7.5 with Java 6 and Tomcat 6.0.24.

The latest version of Tomcat, version 6.0.24, has introduced a new MemoryLeakDetector valve that during application shutdown dumps a list of threads left running, ThreadLocals not removed, etc. I’m trying to debug the shutdown of my application trying to figure out how to clean up these things left behind. However, MyEcplise won’t let me.

When I request that MyEclipse shut down Tomcat, It gives me about 20-30 seconds of debug time, and then kills the process. Can I change this delay, or remove it altogether, or can the delay be suspended while I’m debugging at a breakpoint?

Thanks!

-J.C.

[Brian Fernandes]

JC,
I’m afraid that there is no way to prevent or delay the hard shut down that happens after about 20-30 seconds. I will look at being able to put this in a future MyEclipse release, have filed an enhancement request to see what we can do.

For now, perhaps you could shut down the server externally instead of using the “Stop” action within MyEclipse?

[Author]

Posts