（未解决问题）Tomcat undeploy does not remove web application artifacts

最新推荐文章于 2023-10-02 17:19:34 发布

原创最新推荐文章于 2023-10-02 17:19:34 发布 · 233 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#java

J2EE 专栏收录该内容

20 篇文章

订阅专栏

本文探讨了在Tomcat中卸载应用程序时可能遇到的问题，特别是当应用程序由于后台线程或长时间运行的请求而无法完全卸载的情况。文章建议检查日志文件和获取线程转储来定位问题，并提醒开发者注意重新部署应用程序可能导致的内存问题。

源：http://stackoverflow.com/questions/484271/tomcat-undeploy-does-not-remove-web-application-artifacts
评：
2 down vote accepted

It might be that your application cannot completely be undeployed because there are background threads (that you most likely started yourself) or long running requests that are preventing the application to stop completely.

Did you inspect the log files? Did they state if the application could be undeployed successfully? Or the opposite? Can you get a Thread dump after you attempted to undeploy (kill -3 processid on Unix, Ctrl-Break in a console in Windows) and see if there is something still running that shouldn't?

Also note that most applications I've seen cannot be undeployed completely with regard to the memory they took. I've run into OutOfMemoryErrors (PermGen) quite often, especially after redeploying webapps (you'll find a lot of references on PermGen if you google for it) therefor I believe redeploying is ok for development machines, but not for production ones. It's better to know this before you're puzzled by this in production.