The following web applications were stopped (reloaded, undeployed),
but their classes from previous runs are still loaded in memory, thus causing a memory leak (use a profiler to confirm):
使用Maven 在Tomcat 上 重新部署项目时内存泄漏,原因之前的classes没有卸载还存在 jvm 内存中,
不过在有博主说在卸载项目之前先 stop一下项目,再 undeploy 就不会出现 memory leak
Stack Overflow:
If you want to make sure not to cause leaks you have to do the following:
- Make sure your web application does not use any java classes that are in the web container shared libraries. If you have any shared libraries, make sure there is no strong references to the objects in those libraries
- Avoid using static variables, especially on java objects like HashTable, Sets, etc. If you need to, make sure that you call remove to release the objects with the maps, lists…
Here is also a good article on ThreadLocal and MemoryLeaks - http://blog.arendsen.net/index.php/2005/02/22/threadlocals-and-memory-leaks-revisited/
1是避免使用容器中的库,如果非要使用,避免使用强引用指向那些库
2是避免使用静态变量,特别是把map,set等容器作为静态变量