tomcat-web项目运行一段时间就宕掉了，警告: processCallbacks status 2

问题描述

web项目运行一段时间就宕掉了，警告: processCallbacks status 2

以下是日志信息，请大家帮忙看下：

2014-05-07 20:03:57 Commons Daemon procrun stderr initialized
2014-5-7 20:03:59 org.apache.catalina.core.AprLifecycleListener init
信息: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: E:search_onlinestandard-tomcat-6.0.29bin;.;C:WINDOWSSunJavabin;C:WINDOWSsystem32;C:WINDOWS;c:Ora10InstantClientbin;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;C:Javajdk1.6.0_21lib;C:Javajdk1.6.0_21bin;C:Program FilesDellSysMgtomabin;C:Program FilesDellSysMgtidrac;C:Program FilesMicrosoft SQL Server80ToolsBinn;C:Program FilesMicrosoft SQL Server90DTSBinn;C:Program FilesMicrosoft SQL Server90Toolsbinn;C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDE;C:Program FilesMicrosoft Visual Studio 8Common7IDEPrivateAssemblies
2014-5-7 20:03:59 org.apache.catalina.startup.Catalina load
信息: Initialization processed in 761 ms
2014-5-7 20:03:59 org.apache.catalina.core.StandardService start
信息: Starting service EmpSearchPro
2014-5-7 20:03:59 org.apache.catalina.core.StandardEngine start
信息: Starting Servlet Engine: Apache Tomcat/6.0.29
2014-5-7 20:04:00 org.apache.catalina.core.ApplicationContext log
信息: Initializing Spring root WebApplicationContext
2014-5-7 20:04:02 org.apache.catalina.startup.HostConfig deployDescriptor
信息: Deploying configuration descriptor host-manager.xml
2014-5-7 20:04:02 org.apache.catalina.startup.HostConfig deployDescriptor
信息: Deploying configuration descriptor manager.xml
2014-5-7 20:04:02 org.apache.catalina.startup.HostConfig deployDirectory
信息: Deploying web application directory docs
2014-5-7 20:04:02 org.apache.catalina.startup.HostConfig deployDirectory
信息: Deploying web application directory examples
2014-5-7 20:04:02 org.apache.catalina.core.ApplicationContext log
信息: ContextListener: contextInitialized()
2014-5-7 20:04:02 org.apache.catalina.core.ApplicationContext log
信息: SessionListener: contextInitialized()
2014-5-7 20:04:02 org.apache.catalina.startup.HostConfig deployDirectory
信息: Deploying web application directory WebQuery
2014-5-7 20:04:03 org.apache.catalina.core.ApplicationContext log
信息: Initializing Spring root WebApplicationContext
2014-5-7 20:04:04 org.apache.jk.common.ChannelSocket init
信息: JK: ajp13 listening on /0.0.0.0:8009
2014-5-7 20:04:04 org.apache.jk.server.JkMain start
信息: Jk running ID=0 time=0/78 config=null
2014-5-7 20:04:04 org.apache.catalina.startup.Catalina start
信息: Server startup in 4629 ms
2014-5-8 9:59:06 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 9:59:08 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 9:59:30 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 10:24:51 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 10:24:53 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 10:24:56 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 10:25:11 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 17:43:01 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 17:44:40 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 18:18:41 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 18:19:02 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 18:19:14 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 18:20:06 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 18:22:07 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 18:22:46 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 18:23:06 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 18:34:39 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 18:35:24 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 20:00:44 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 20:01:29 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 20:01:57 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 20:02:25 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-8 20:02:52 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-9 9:35:57 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-9 10:44:22 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-9 11:38:34 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-9 11:38:39 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-9 12:48:51 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-9 13:29:28 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-9 13:30:33 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-9 13:30:43 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-9 16:07:07 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-9 16:07:07 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-9 16:15:35 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-9 18:22:24 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-10 12:35:22 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-10 13:45:59 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-10 13:48:08 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-10 13:48:38 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-10 13:48:49 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-10 13:49:08 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 13:07:58 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 13:09:47 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 14:32:39 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 14:33:11 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 14:34:14 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 14:34:32 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 14:40:08 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 14:42:42 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 14:43:31 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 14:46:53 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 16:04:39 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 16:06:31 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 16:47:14 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 16:48:04 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 16:49:08 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 16:50:33 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 17:04:46 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 17:05:49 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 17:23:43 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 17:24:52 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 19:01:26 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 19:04:00 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 19:04:01 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 19:04:01 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 19:10:35 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-11 19:11:05 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-12 10:38:58 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-12 12:02:52 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-12 12:03:17 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-12 15:11:51 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-12 15:55:16 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-12 15:55:54 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-12 15:55:55 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-12 15:56:20 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-12 16:29:55 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-12 17:09:33 org.apache.jk.common.ChannelSocket processConnection
警告: processCallbacks status 2
2014-5-13 8:59:49 org.apache.catalina.core.StandardService stop
信息: Stopping service EmpSearchPro
2014-5-13 8:59:49 org.apache.catalina.core.ApplicationContext log
信息: SessionListener: contextDestroyed()
2014-5-13 8:59:49 org.apache.catalina.core.ApplicationContext log
信息: ContextListener: contextDestroyed()
2014-5-13 8:59:50 org.apache.catalina.core.ApplicationContext log
信息: Closing Spring root WebApplicationContext
2014-5-13 8:59:50 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
严重: The web application [/WebQuery] registered the JBDC driver [oracle.jdbc.driver.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
2014-5-13 8:59:50 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
严重: The web application [/WebQuery] created a ThreadLocal with key of type null and a value of type java.lang.Object[] but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
2014-5-13 8:59:51 org.apache.catalina.core.StandardWrapper unload
信息: Waiting for 538 instance(s) to be deallocated
2014-5-13 8:59:52 org.apache.catalina.core.StandardWrapper unload
信息: Waiting for 538 instance(s) to be deallocated
2014-5-13 8:59:53 org.apache.catalina.core.StandardWrapper unload
信息: Waiting for 538 instance(s) to be deallocated
2014-5-13 8:59:54 org.apache.catalina.core.ApplicationContext log
信息: Closing Spring root WebApplicationContext
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
严重: The web application [] registered the JBDC 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.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
严重: The web application [] registered the JBDC driver [oracle.jdbc.driver.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] appears to have started a thread named [AWT-Windows] but has failed to stop it. This is very likely to create a memory leak.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
2014-5-13 8:59:54 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.

时间： 2024-10-03 06:02:05

tomcat-web项目运行一段时间就宕掉了，警告: processCallbacks status 2的相关文章

内存溢出-tomcat7运行一段时间总是死掉

问题描述 tomcat7运行一段时间总是死掉 这是打印的错误日志: # A fatal error has been detected by the Java Runtime Environment: # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006d9d6262, pid=4864, tid=3628 # JRE version: 6.0_27-b07 Java VM: Java HotSpot(TM) 64-Bit Ser

Hibernate项目运行一段时间后出错

问题描述 错误如下:org.hibernate.exception.JDBCConnectionException:couldnotexecutequerycom.microsoft.sqlserver.jdbc.SQLServerException:Connectionreset代码:publicListUserData(StringqueryStr){Sessionsession=HibernateSessionFactory.getSession();Transactionts=sessi

tomcat服务器使用一段时间后宕掉，各位帮忙看看怎么解决

问题描述 tomcat版本 6.0.32,jdk1.6.23严重: The web application [] registered the JDBC driver [org.apache.derby.jdbc.AutoloadedDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly

java-项目运行一段时间后session数据失效问题

问题描述 项目运行一段时间后session数据失效问题 最近struts2+spring做开发,项目启动后登陆操作一切正常,一天后再登陆后操作session里的数据老是失效不存在,但是页面又显示正常, 纠结了很久找不到原因,还请大神们帮忙看下. 获取session数据是用struts2的方法,代码如下,服务器是用的jboss7 HttpServletRequest request = ServletActionContext.getRequest(); HttpSession session =

内存溢出 tomcat-项目运行一段时间后网页就打不开了，有时候没有报错，有时候会报下面的错误，求大神指教

问题描述 项目运行一段时间后网页就打不开了,有时候没有报错,有时候会报下面的错误,求大神指教 不知道是不是跟内存溢出有关系 解决方案 这应该不是内存溢出问题,报的是空指针,有可能的是某些请求参数时间过长失效 解决方案二: 空指针异常 看一下是否有空指针 如果没有 重启服务器 解决方案三: 空指针异常 看一下是否有空指针 如果没有 重启服务器

内存泄露-TOMCAT运行一段时间后抛找不到主机异常，紧急。。。。。。。。。

问题描述 TOMCAT运行一段时间后抛找不到主机异常,紧急......... TOMCAT运行一段时间后报:ava.net.UnknownHostException: 主机名,主机名:unknown error at java.net.InetAddress.getLocalHost(InetAddress.java:1484) at org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:490) at org.ap

tomcat退出-Tomcat运行一段时间后自动退出

问题描述 Tomcat运行一段时间后自动退出 最近tomcat运行一个项目,运行一两天就自动关闭,也没有报错. 以下是网上查找别人说的原因: 1,并发用户数目过大,也会导致tomcat自动停止服务. 2,系统本身的网络负载平衡没有做好,导致tomcat自动停止服务: 3,程序迭代不合理也是一个原因: 4,数据库连接未关闭,导致资源损耗过重,会引起服务停止: 5,程序严重错误,也会引起tomcat停止服务! 想请问以下,除以上外,还有什么原因会引起tomcat自动关闭.有什么软件可以测试或者模拟异

tomcat运行一段时间后页面报HTTP Status 500

问题描述 web网页在运行一段时间后就出现HTTPStatus500错误,重新启动Tomcat后又正常.出现信息:typeExceptionreportmessagedescriptionTheserverencounteredaninternalerror()thatpreventeditfromfulfillingthisrequest.exceptionorg.apache.jasper.JasperExceptionorg.apache.jasper.servlet.JspServlet

程序运行一段时间，tomcat无反应，页面显示白页，不跳转

问题描述 程序运行一段时间,tomcat无反应,页面显示白页,不跳转 程序部署一段时间后,正常运行很久,但是最近出现了一种情况.当点击某个action类进行跳转的时候 页面无响应,tomcat后台也没有log输出,只有重新启动才能解决问题. 想问问这种情况是如何产生的,有什么好的解决方法,谢谢