tomcat 启动一段时间后报错，然后自动重启

TommyWu01 2018-06-07 02:24:28

tomcat 启动一段时间后报错，然后自动重启，之后就没事了，不知道什么原因导致的。

框架是springMVC+maven，用了redis 和 ehcache

六月 07, 2018 2:19:33 下午 org.apache.catalina.core.StandardContext reload

信息: Reloading Context with name [/hub-sdk-java] has started

六月 07, 2018 2:19:33 下午 org.apache.catalina.core.ApplicationContext log

信息: Destroying Spring FrameworkServlet 'hub-sdk-java'

2018-六月-07 14:19:33-[TS] INFO ContainerBackgroundProcessor[StandardEngine[Catalina]] org.springframework.web.context.support.XmlWebApplicationContext - Closing WebApplicationContext for namespace 'hub-sdk-java-servlet': startup date [Thu Jun 07 14:19:20 CST 2018]; parent: Root WebApplicationContext

六月 07, 2018 2:19:33 下午 org.apache.catalina.core.ApplicationContext log

信息: Shutting down log4j

六月 07, 2018 2:19:33 下午 org.apache.catalina.core.ApplicationContext log

信息: Closing Spring root WebApplicationContext

log4j:WARN No appenders could be found for logger (org.springframework.web.context.support.XmlWebApplicationContext).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

六月 07, 2018 2:19:33 下午 org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads

警告: The web application [hub-sdk-java] appears to have started a thread named [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:

 java.lang.Object.wait(Native Method)

 org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:568)

六月 07, 2018 2:19:33 下午 org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads

警告: The web application [hub-sdk-java] appears to have started a thread named [__DEFAULT__] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:

 java.lang.Object.wait(Native Method)

 java.lang.Object.wait(Object.java:502)

 java.util.TimerThread.mainLoop(Timer.java:526)

 java.util.TimerThread.run(Timer.java:505)

六月 07, 2018 2:19:33 下午 org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads

警告: The web application [hub-sdk-java] appears to have started a thread named [bike%0052esult902%0041nt%004cist.data] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:

 sun.misc.Unsafe.park(Native Method)

 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)

 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)

 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)

 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)

 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067)

 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)

 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

 java.lang.Thread.run(Thread.java:748)

六月 07, 2018 2:19:36 下午 org.apache.jasper.servlet.TldScanner scanJars

信息: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.

六月 07, 2018 2:19:36 下午 org.apache.catalina.core.ApplicationContext log

信息: No Spring WebApplicationInitializer types detected on classpath

六月 07, 2018 2:19:37 下午 org.apache.catalina.core.ApplicationContext log

信息: Initializing Spring root WebApplicationContext

2018-六月-07 14:19:37-[TS] INFO ContainerBackgroundProcessor[StandardEngine[Catalina]] org.springframework.web.context.ContextLoader - Root WebApplicationContext: initialization started

2018-六月-07 14:19:37-[TS] INFO ContainerBackgroundProcessor[StandardEngine[Catalina]] org.springframework.web.context.support.XmlWebApplicationContext - Refreshing Root WebApplicationContext: startup date [Thu Jun 07 14:19:37 CST 2018]; root of context hierarchy

2018-六月-07 14:19:37-[TS] INFO ContainerBackgroundProcessor[StandardEngine[Catalina]] org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading XML bean definitions from file [D:\apache-tomcat-8.0.30\webapps\hub-sdk-java\WEB-INF\classes\applicationContext.xml]

2018-六月-07 14:19:37-[TS] INFO ContainerBackgroundProcessor[StandardEngine[Catalina]] org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor - JSR-330 'javax.inject.Inject' annotation found and supported for autowiring

2018-六月-07 14:19:37-[TS] INFO ContainerBackgroundProcessor[StandardEngine[Catalina]] org.quartz.impl.StdSchedulerFactory - Using default implementation for ThreadExecutor

2018-六月-07 14:19:37-[TS] INFO ContainerBackgroundProcessor[StandardEngine[Catalina]] org.quartz.core.SchedulerSignalerImpl - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl

2018-六月-07 14:19:37-[TS] INFO ContainerBackgroundProcessor[StandardEngine[Catalina]] org.quartz.core.QuartzScheduler - Quartz Scheduler v.2.2.1 created.

2018-六月-07 14:19:42-[TS] WARN http-apr-8080-exec-6 net.sf.ehcache.DiskStorePathManager - diskStorePath 'C:\Users\playboy\AppData\Local\Temp' is already used by an existing CacheManager either in the same VM or in a different process.

The diskStore path for this CacheManager will be set to C:\Users\playboy\AppData\Local\Temp\ehcache_auto_created3780323549391590031diskstore.

To avoid this warning consider using the CacheManager factory methods to create a singleton CacheManager or specifying a separate ehcache configuration (ehcache.xml) for each CacheManager instance.

六月 07, 2018 2:24:28 下午 org.apache.catalina.loader.WebappClassLoaderBase checkStateForResourceLoading

信息: Illegal access: this web application instance has been stopped already. Could not load [java.lang.OutOfMemoryError]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.

java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [java.lang.OutOfMemoryError]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.

	at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1353)

	at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1341)

	at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1206)

	at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1167)

	at net.sf.ehcache.util.concurrent.ConcurrentHashMap.values(ConcurrentHashMap.java:2722)

	at net.sf.ehcache.util.concurrent.ConcurrentHashMap.values(ConcurrentHashMap.java:220)

	at net.sf.ehcache.statistics.extended.ExtendedStatisticsImpl$1.run(ExtendedStatisticsImpl.java:104)

	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)

	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)

	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

	at java.lang.Thread.run(Thread.java:748)