开发者社区> 问答> 正文

tomcat7莫名重启


部署在阿里云ECS上的tomcat7总是莫名重启,日志如下,大侠给指点下。






Aug 28, 2015 10:11:54 AM org.apache.catalina.core.StandardServer await
INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance.
Aug 28, 2015 10:11:54 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-8080"]
Aug 28, 2015 10:11:54 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-8443"]
Aug 28, 2015 10:11:54 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["ajp-bio-8009"]
Aug 28, 2015 10:11:54 AM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Aug 28, 2015 10:11:54 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/SCRM] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Aug 28, 2015 10:11:54 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/SCRM] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak.
Aug 28, 2015 10:11:54 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/worklite] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Aug 28, 2015 10:11:54 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/worklite] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak.
Aug 28, 2015 10:11:54 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/worklite] appears to have started a thread named [org.springframework.scheduling.quartz.SchedulerFactoryBean#2_Worker-6] but has failed to stop it. This is very likely to create a memory leak.
Aug 28, 2015 10:11:54 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SEVERE: The web application [/worklite] created a ThreadLocal with key of type [org.springframework.core.NamedThreadLocal] (value [Current AOP method invocation]) and a value of type [org.springframework.aop.framework.CglibAopProxy.CglibMethodInvocation] (value [ReflectiveMethodInvocation: public java.util.ArrayList com.worklite.business.calls.calls.calls.service.CallsServiceImpl.doWithMsgHistory(); target is of class [com.worklite.business.calls.calls.calls.service.CallsServiceImpl]]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
Aug 28, 2015 10:11:54 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SEVERE: The web application [/worklite] created a ThreadLocal with key of type [org.apache.http.impl.cookie.DateUtils$DateFormatHolder$1] (value [org.apache.http.impl.cookie.DateUtils$DateFormatHolder$1@5cb7428f]) and a value of type [java.lang.ref.SoftReference] (value [java.lang.ref.SoftReference@372e9d7]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
Aug 28, 2015 10:11:54 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
Aug 28, 2015 10:11:54 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SEVERE: The web application [/worklite] created a ThreadLocal with key of type [org.springframework.core.NamedThreadLocal] (value [Current aspect-driven transaction]) and a value of type [org.springframework.transaction.interceptor.TransactionAspectSupport.TransactionInfo] (value [Unknown]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
Aug 28, 2015 10:11:54 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-8080"]
Aug 28, 2015 10:11:54 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-8443"]
Aug 28, 2015 10:11:54 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["ajp-bio-8009"]
Aug 28, 2015 10:11:54 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-8080"]
Aug 28, 2015 10:11:54 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-8443"]
Aug 28, 2015 10:11:54 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["ajp-bio-8009"]
Aug 28, 2015 10:11:55 AM org.apache.catalina.loader.WebappClassLoader loadClass
Aug 28, 2015 10:11:57 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
Aug 28, 2015 10:11:58 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Aug 28, 2015 10:11:58 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8443"]
Aug 28, 2015 10:11:58 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Aug 28, 2015 10:11:58 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1607 ms
Aug 28, 2015 10:11:58 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Aug 28, 2015 10:11:58 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.54
Aug 28, 2015 10:11:58 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/share/tomcat7/webapps/ROOT
Aug 28, 2015 10:12:00 AM org.apache.tomcat.websocket.server.WsSci onStartup
INFO: JSR 356 WebSocket (Java WebSocket 1.0) support is not available when running on Java 6. To suppress this message, run Tomcat on Java 7, remove the WebSocket JARs from $CATALINA_HOME/lib or add the WebSocket JARs to the tomcat.util.scan.DefaultJarScanner.jarsToSkip property in $CATALINA_BASE/conf/catalina.properties. Note that the deprecated Tomcat 7 WebSocket API will be available.
Aug 28, 2015 10:12:00 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /usr/share/tomcat7/webapps/ROOT has finished in 1,384 ms
Aug 28, 2015 10:12:00 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/share/tomcat7/webapps/worklite

展开
收起
狐狸云 2015-08-28 12:25:58 12455 0
2 条回答
写回答
取消 提交回答
  • 一个程序员,欢迎骚扰!!!
    LZ看一下 这片文章 基本是这个问题: http://my.oschina.net/u/1157906/blog/199794

    还有重启tomcat 必须要杀掉进程号。如果不kill的话,这种java进程越来越多。
    2015-08-28 16:56:07
    赞同 展开评论 打赏
  • 旺旺:nectar2。
    楼主您好,

    请问您的ECS是什么系统,配置的内存是多少?

    这一句,仿佛是告诉我们,ECS里的内存好象不够用了。如果是Linux,或许您可以创建swap分区,以缓解这种内存不足的现象。

    SEVERE: The web application [/SCRM] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak.

    2015-08-28 14:34:18
    赞同 展开评论 打赏
问答排行榜
最热
最新

相关电子书

更多
Apache Tomcat 的云原生演进 立即下载
低代码开发师(初级)实战教程 立即下载
阿里巴巴DevOps 最佳实践手册 立即下载