设为首页 收藏本站
查看: 628|回复: 0

[经验分享] tomcat shutdown后清理工作出现的异常

[复制链接]

尚未签到

发表于 2018-12-1 08:26:46 | 显示全部楼层 |阅读模式
  引言

  tomcat属于web应用服务器,当我们的应用服务器关闭后,但是有些java class/thread/threadLocal等依然存活,当再次reload后,就会导致内存的溢出.为了避免这种严重的内存leak问题,tomcat做了一些内存溢出检测.
  server.xml
  
  
  
    虽然tomcat做了这些检测并试图stop这些存活的引用,但是不是强制的,比如一些请求或线程,当应用关闭的时候,还在处理中,这时tomcat不会去关闭.这就需要tomcat强制关闭或依赖对应的框架来关闭.
  

  项目中遇到类似问题
Q1:
    org.apache.catalina.loader.WebappClassLoaderclearReferencesJdbc
SEVERE:The web application [/myapp] registered the JDBC driver[com.mysql.jdbc.Driver] but failed to unregister it when the web applicationwas stopped. To prevent a memory leak, the JDBC Driver has been forciblyunregistered.
A1:
https://stackoverflow.com/questions/15632153/tomcat7-jdbc-datasource-this-is-very-likely-to-create-a-memory-leak
需要把项目中使用的jdbc驱动包放到tomcat/lib

Q2:
org.apache.catalina.loader.WebappClassLoaderclearReferencesThreads
SEVERE: The web application [/myapp] appears to have started athread named [Abandoned connection cleanup thread] but has failed to stop it.This is very likely to create a memory leak.
A2:
   https://stackoverflow.com/questions/24850091/the-web-application-registered-the-jdbc-driver-com-mysql-jdbc-driver-but-fa

Q3:
SEVERE:The web application [/myapp] appears to have started a thread named [MySQL StatementCancellation Timer] but has failed to stop it. This is very likely to create amemory leak.
A3:
https://stackoverflow.com/questions/10615118/how-to-solve-memory-leak-problems
  这是mysql jdbc 驱动包的一个BUG(SUNVM), https://bugs.mysql.com/bug.php?id=36565
  version 5.1.27之后的版本解决了这个问题.

Q4:
org.apache.catalina.loader.WebappClassLoadercheckThreadLocalMapForLeaks
SEVERE: The web application [/myapp] created a ThreadLocal with keyof type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@681f8054]) and avalue of type [com.alibaba.druid.wall.spi.WallVisitorUtils.WallTopStatementContext](value[com.alibaba.druid.wall.spi.WallVisitorUtils$WallTopStatementContext@117d5a14])but failed to remove it when the web application was stopped. Threads are goingto be renewed over time to try and avoid a probable memory leak.
A4:
    关闭druid的自带监测功能.  

  tomcat 释放引用的主要分类

  

  1. org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
    http://hongjiang.info/tomcat-jdbc-leak-prevention/
    https://stackoverflow.com/questions/15632153/tomcat7-jdbc-datasource-this-is-very-likely-to-create-a-memory-leak
  把JDBC driver放到tomcat/lib下,并删除项目的jdbc driver.
  

  2. org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
  http://hongjiang.info/tomcat-clear-references-threads/
  

  

  3. org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
  http://hongjiang.info/tomcat-clear-references-threadlocal/
  

  

  4. clearReferencesRmiTargets
  

  

  5.clearReferencesStaticFinal
  

  

  6.clearReferencesResourceBundles
  

  protected void clearReferences() {   // De-register any remaining JDBC drivers   clearReferencesJdbc();   // Stop any threads the web application started   clearReferencesThreads();   // Check for leaks triggered by ThreadLocals loaded by this class loader   checkThreadLocalsForLeaks();   // Clear RMI Targets loaded by this class loader   clearReferencesRmiTargets();   // Null out any static or final fields from loaded classes,   // as a workaround for apparent garbage collection bugs   if (clearReferencesStatic) {       clearReferencesStaticFinal();   }    // Clear the IntrospectionUtils cache.   IntrospectionUtils.clear();   // Clear the classloader reference in common-logging   if (clearReferencesLogFactoryRelease) {       org.apache.juli.logging.LogFactory.release(this);   }   // Clear the resource bundle cache   // This shouldn't be necessary, the cache uses weak references but   // it has caused leaks. Oddly, using the leak detection code in   // standard host allows the class loader to be GC'd. This has been seen   // on Sun but not IBM JREs. Maybe a bug in Sun's GC impl?   clearReferencesResourceBundles();   // Clear the classloader reference in the VM's bean introspector   java.beans.Introspector.flushCaches();}
  

  tomcat graceful shutdown
  https://dzone.com/articles/tomcats-graceful-shutdown
  http://www.captaindebug.com/2013/09/tomcats-graceful-shutdown-with-daemons.html#.Wdxh9ltL_IU
  

  

  

  

  参考文档:
  http://hongjiang.info/tomcat-jdbc-leak-prevention/
  http://hongjiang.info/tomcat-clear-references-threads/
  http://hongjiang.info/tomcat-clear-references-threadlocal/
  http://blog.csdn.net/will_awoke/article/details/38338519
  http://www.cnblogs.com/lixiaojiao-hit/p/5095180.html
  

  

  





运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-641774-1-1.html 上篇帖子: ansible之配置tomcat 下篇帖子: java Struts 修改本身的struts.xml,web.xml等后不用再次重启tomcat
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表