[jboss-user] [Tomcat, HTTPD, Servlets & JSP] - Major problem using error-page element in web.xml
Hi,
I have a JBoss installation running on SUSE Linux which has been running without problems
for many months.
A few days ago, I added a simple <error-page> element to the web.xml file of one of
my applications:
<error-page>
| <error-code>404</error-code>
| <location>/default.jsp</location>
| </error-page>
A few hours after adding this, my server stopped responding. I checked the logs and found
a whole slew of "too many open files" errors. I did not think this was related
to my error page at the time. I upped the open file limit on my server from 1024 to 32768,
and restarted JBoss.
Three days later, the same error has appeared. At the same time, I am also noticing
thousands of these errors in my log:
2007-02-04 00:04:27,892 WARN
[org.apache.catalina.core.ContainerBase.[jboss.web].[june.zanne.com]] Exception Processing
ErrorPage[errorCode=404, location=/default.jsp]
ClientAbortException: java.net.SocketException: Connection reset
at
org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:327)
at
org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:293)
at
org.apache.catalina.connector.Response.flushBuffer(Response.java:534)
at
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:285)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.valves.FastCommonAccessLogValve.invoke(FastCommonAccessLogValve.java:481)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:619)
I have never seen this kind of exception in my logs before.
My suspicion is that the problems are related - that the Socket exception is leaking file
handles, which eventually leads to all my file handles being exhaused.
Has anyone seen this before?
Thanks,
Frank
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011073#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...