Re: Connection aborted by peer: socket write error
but my server.xml as below, shows there is enough available threads. And only 10 threads are attacking. On Tue, 11 Jun 2002 09:33:55 +0530 Anand Bashyam Narasimhan <[EMAIL PROTECTED]> wrote: > Typically the error that you are getting on the server side "connection > reset by peer" happens when a connection to the servlet is open and while > the request is being processed the stream to which the response is written > back is closed abruptly. You can easily replicate this with a simple > servlet, that proceses a GET request, and then put a sleep for "n" seconds > and lets say you are request it through a browser, close the browser session > at n-m(m>1) seconds and u'll see this error. > > As for the threads and the total connection that can be opened up, these can > be configured in the server.xml for TC. It's an attribute to the > "HttpConnector" > > port="9090" minProcessors="5" maxProcessors="75" >enableLookups="true" redirectPort="8443" >acceptCount="10" debug="0" connectionTimeout="6"/> > > Try to increase this and see if you are able to get more connections. > Normally these connections that come with TC4 default are more than enough > for development mode testing of any web-app. > > Hope that helps. > > Anand > -Original Message- > From: Leon [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, June 11, 2002 8:11 AM > To: [EMAIL PROTECTED] > Subject: Connection aborted by peer: socket write error > > > With Tomcat 4.0.3, i lanuched my serverlet, XMLSevlet, but only under 10 > threads continuously connect, the client program threw the below > exception. And Tomcat also showed exception described as below (server > side exception). > > I searched in the archieve, and it seems that this bug has already found > and fixed in 4.0.3. But why it happens again? > > Anyone can do me a favor? > > java.io.FileNotFoundException: > http://localhost:18080/XMLDBService/servlet/XMLServlet > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection > .java:574) > at > com.foo.client.connection.IpedoURLConnection.sendPostMessage(IpedoURLConnect > ion.java:104) > at > com.foo.client.impl.ClientImplTool.processCommand(ClientImplTool.java:150) > at > com.foo.client.impl.ClientImplTool.processCommand(ClientImplTool.java:113) > at > com.foo.cursor.client.ClientCacheManager.getNode(ClientCacheManager.java:171 > ) > at com.foo.client.dom.UNode.getNode(UNode.java:798) > at com.foo.client.dom.UChildNode.getNextSibling(UChildNode.java:88) > at > com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:761) > at > com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:597) > at > com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja > va:1180) > at > com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:760) > at > com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:597) > at > com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja > va:1180) > at > com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja > va:1105) > at > com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja > va:1248) > at > com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja > va:1105) > at > com.foo.serialize.BaseMarkupSerializer.serializeXPathReturnNode(BaseMarkupSe > rializer.java:461) > at com.foo.utils.CommonTool.writeNode(CommonTool.java:100) > at com.foo.cdctest.cursor.GetDocument.runTest(GetDocument.java:93) > at > com.foo.cdctest.testframework.driver.CaseDriver.run(CaseDriver.java:46) > at java.lang.Thread.run(Thread.java:484) > [13] I/O error encountered while performing the > operation.http://localhost:18080/XMLDBService/servlet/XMLServlet > at > com.foo.client.impl.ClientImplTool.processCommand(ClientImplTool.java:160) > at > com.foo.client.impl.ClientImplTool.processCommand(ClientImplTool.java:113) > at > com.foo.cursor.client.ClientCacheManager.getNode(ClientCacheManager.java:171 > ) > at com.foo.client.dom.UNode.getNode(UNode.java:798) > at com.foo.client.dom.UChildNode.getNextSibling(UChildNode.java:88) > at > com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:761) > at > com.foo.serialize.XMLSeria
RE: Connection aborted by peer: socket write error
Typically the error that you are getting on the server side "connection reset by peer" happens when a connection to the servlet is open and while the request is being processed the stream to which the response is written back is closed abruptly. You can easily replicate this with a simple servlet, that proceses a GET request, and then put a sleep for "n" seconds and lets say you are request it through a browser, close the browser session at n-m(m>1) seconds and u'll see this error. As for the threads and the total connection that can be opened up, these can be configured in the server.xml for TC. It's an attribute to the "HttpConnector" Try to increase this and see if you are able to get more connections. Normally these connections that come with TC4 default are more than enough for development mode testing of any web-app. Hope that helps. Anand -Original Message- From: Leon [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 8:11 AM To: [EMAIL PROTECTED] Subject: Connection aborted by peer: socket write error With Tomcat 4.0.3, i lanuched my serverlet, XMLSevlet, but only under 10 threads continuously connect, the client program threw the below exception. And Tomcat also showed exception described as below (server side exception). I searched in the archieve, and it seems that this bug has already found and fixed in 4.0.3. But why it happens again? Anyone can do me a favor? java.io.FileNotFoundException: http://localhost:18080/XMLDBService/servlet/XMLServlet at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection .java:574) at com.foo.client.connection.IpedoURLConnection.sendPostMessage(IpedoURLConnect ion.java:104) at com.foo.client.impl.ClientImplTool.processCommand(ClientImplTool.java:150) at com.foo.client.impl.ClientImplTool.processCommand(ClientImplTool.java:113) at com.foo.cursor.client.ClientCacheManager.getNode(ClientCacheManager.java:171 ) at com.foo.client.dom.UNode.getNode(UNode.java:798) at com.foo.client.dom.UChildNode.getNextSibling(UChildNode.java:88) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:761) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:597) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja va:1180) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:760) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:597) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja va:1180) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja va:1105) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja va:1248) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja va:1105) at com.foo.serialize.BaseMarkupSerializer.serializeXPathReturnNode(BaseMarkupSe rializer.java:461) at com.foo.utils.CommonTool.writeNode(CommonTool.java:100) at com.foo.cdctest.cursor.GetDocument.runTest(GetDocument.java:93) at com.foo.cdctest.testframework.driver.CaseDriver.run(CaseDriver.java:46) at java.lang.Thread.run(Thread.java:484) [13] I/O error encountered while performing the operation.http://localhost:18080/XMLDBService/servlet/XMLServlet at com.foo.client.impl.ClientImplTool.processCommand(ClientImplTool.java:160) at com.foo.client.impl.ClientImplTool.processCommand(ClientImplTool.java:113) at com.foo.cursor.client.ClientCacheManager.getNode(ClientCacheManager.java:171 ) at com.foo.client.dom.UNode.getNode(UNode.java:798) at com.foo.client.dom.UChildNode.getNextSibling(UChildNode.java:88) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:761) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:597) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja va:1180) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:760) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:597) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja va:1180) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja va:1105) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja va:1248) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.ja va:1105) at com.foo.serialize.BaseMarkupSerializer.serializeXPathReturnNode(BaseMarkupSe rializer.java:461) at com.foo.utils.CommonTool.writeNode(CommonTool.java:100) at com.foo.cdctest.cursor.GetDocument.runTest(GetDocument.java:93) at com.foo.cdctest.testframework.driver.Ca
Connection aborted by peer: socket write error
With Tomcat 4.0.3, i lanuched my serverlet, XMLSevlet, but only under 10 threads continuously connect, the client program threw the below exception. And Tomcat also showed exception described as below (server side exception). I searched in the archieve, and it seems that this bug has already found and fixed in 4.0.3. But why it happens again? Anyone can do me a favor? java.io.FileNotFoundException: http://localhost:18080/XMLDBService/servlet/XMLServlet at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:574) at com.foo.client.connection.IpedoURLConnection.sendPostMessage(IpedoURLConnection.java:104) at com.foo.client.impl.ClientImplTool.processCommand(ClientImplTool.java:150) at com.foo.client.impl.ClientImplTool.processCommand(ClientImplTool.java:113) at com.foo.cursor.client.ClientCacheManager.getNode(ClientCacheManager.java:171) at com.foo.client.dom.UNode.getNode(UNode.java:798) at com.foo.client.dom.UChildNode.getNextSibling(UChildNode.java:88) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:761) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:597) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.java:1180) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:760) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:597) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.java:1180) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.java:1105) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.java:1248) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.java:1105) at com.foo.serialize.BaseMarkupSerializer.serializeXPathReturnNode(BaseMarkupSerializer.java:461) at com.foo.utils.CommonTool.writeNode(CommonTool.java:100) at com.foo.cdctest.cursor.GetDocument.runTest(GetDocument.java:93) at com.foo.cdctest.testframework.driver.CaseDriver.run(CaseDriver.java:46) at java.lang.Thread.run(Thread.java:484) [13] I/O error encountered while performing the operation.http://localhost:18080/XMLDBService/servlet/XMLServlet at com.foo.client.impl.ClientImplTool.processCommand(ClientImplTool.java:160) at com.foo.client.impl.ClientImplTool.processCommand(ClientImplTool.java:113) at com.foo.cursor.client.ClientCacheManager.getNode(ClientCacheManager.java:171) at com.foo.client.dom.UNode.getNode(UNode.java:798) at com.foo.client.dom.UChildNode.getNextSibling(UChildNode.java:88) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:761) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:597) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.java:1180) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:760) at com.foo.serialize.XMLSerializer.serializeElement(XMLSerializer.java:597) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.java:1180) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.java:1105) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.java:1248) at com.foo.serialize.BaseMarkupSerializer.serializeNode(BaseMarkupSerializer.java:1105) at com.foo.serialize.BaseMarkupSerializer.serializeXPathReturnNode(BaseMarkupSerializer.java:461) at com.foo.utils.CommonTool.writeNode(CommonTool.java:100) at com.foo.cdctest.cursor.GetDocument.runTest(GetDocument.java:93) at com.foo.cdctest.testframework.driver.CaseDriver.run(CaseDriver.java:46) at java.lang.Thread.run(Thread.java:484) Server side: 2002-06-10 16:18:58 StandardWrapperValve[XMLServlet]: Servlet.service() for servlet XMLServlet threw exception java.net.SocketException: Connection aborted by peer: socket write error at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(Unknown Source) at org.apache.catalina.connector.ResponseBase.flushBuffer(ResponseBase.java:679) at org.apache.catalina.connector.HttpResponseBase.flushBuffer(HttpResponseBase.java:757) at org.apache.catalina.connector.ResponseFacade.flushBuffer(ResponseFacade.java:219) at org.apache.catalina.connector.ResponseStream.close(ResponseStream.java:224) at org.apache.catalina.connector.http.HttpResponseStream.close(HttpResponseStream.java:217) at com.foo.server.servlet.XMLServlet.doPost(XMLServlet.java:219) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
RE: Connection aborted by peer: socket write error
it cause by a bug in
org/apache/tomcat/code/BufferedServletOutputStream.java
there is a cicular buffer where it set to 8k, when the html file which have
included files which size is
more then 8k , the above message will occur.
the cicular buffer was not reset after commit.
Below is the source .
public void recycle() {
// System.out.println("Recycle BOS " );
bufferCount = 0;
totalCount = 0;
closed = false;
usingWriter = false;
resA.setBufferCommitted(false); // this is missing in the source.
}
RE: Connection aborted by peer: socket write error
The client (most notably, the browser) closed the socket. Maybe the user hit the "Stop" button. Maybe the browser crashed. You can pretty much ignore this, however you must be aware that writing to servlet's output stream can result in this exception at any time (as users are free to hit "Stop" at any time during connection). Attila. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 26, 2001 8:57 PM > To: [EMAIL PROTECTED] > Subject: Connection aborted by peer: socket write error > > > Whats causing tis error, and how can I get rid of it ? > > Ctx( /Phase2 ): IOException in: R( /Phase2 + > /img/MapInfo.gif > + null) Connection aborted by peer: socket write error > > > > Billy Ciano > MapInfo > Internet Engineer > 1 Global View > Troy,NY 12180 > Main:(518)285-6000 > E-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Connection aborted by peer: socket write error
Whats causing tis error, and how can I get rid of it ? Ctx( /Phase2 ): IOException in: R( /Phase2 + /img/MapInfo.gif + null) Connection aborted by peer: socket write error Billy Ciano MapInfo Internet Engineer 1 Global View Troy,NY 12180 Main:(518)285-6000 E-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
