Error status is as follows
Exception processing errorpage[errorcode=404, location=/404.jsp] ClientAbortException:java.net.SocketException: Connection Reset by Peer:socket write error 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:544) at Org.apache.catalina.core.StandardHostValve.status (standardhostvalve.java:286) at Org.apache.catalina.core.StandardHostValve.invoke (standardhostvalve.java:136) at Org.apache.catalina.valves.ErrorReportValve.invoke (errorreportvalve.java:105) 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:869) at Org.apache.coyote.http11.http11baseprotocol$http11connectionhandler.processconnection (Http11BaseProtocol.java : 667) at Org.apache.Tomcat.util.net.PoolTcpEndpoint.processSocket (pooltcpendpoint.java:527) at Org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (leaderfollowerworkerthread.java:80) at Org.apache.tomcat.util.threads.threadpool$controlrunnable.run (threadpool.java:684) at Java.lang.Thread.run ( thread.java:595) caused by:java.net.SocketException:Connection reset by Peer:socket write error at JAVA.NET.SOCKETOUTPU Tstream.socketwrite0 (Native method) at Java.net.SocketOutputStream.socketWrite (socketoutputstream.java:92) at Java.net.SocketOutputStream.write (socketoutputstream.java:136) at Org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes (internaloutputbuffer.java:746) at Org.apache.tomcat.util.buf.ByteChunk.flushBuffer (bytechunk.java:433) at Org.apache.coyote.http11.InternalOutputBuffer.flush (internaloutputbuffer.java:304) at Org.apache.coyote.http11.Http11Processor.action (http11processor.java:991) at Org.apache.coyote.Response.action ( response.java:182) at ORG.APACHE.CATALINA.CONNECTOR.OUTPUTbuffer.doflush (outputbuffer.java:322)
is typically set over the
<error-page>
<error-code>404</error-code>
<location>/error.jsp</location>
</error-page>
The system automatically turns to the page and causes this exception to be repeatedly thrown
Workaround:
Modify ERROR.JSP Code
error.jsp use Response.sendredirect ("/index.html");
The main problem is IE7 does not normally parse the application server to the jump information, we need to write our own code display by the server redirected to the new page (JSP)
Sample code is as follows:
<%@ page language= "java" contenttype= "text/html; CHARSET=GBK "pageencoding=" GBK "%> <%@ page import=" org.apache.commons.logging.* "%>
Run again, problem solved