Re: Suppress Connection reset by peer: socket write error.
Dola Woolfe [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi, I apologize for asking this question again for I remembering asking this question in the past, but I can't find the response. What setting (and where) will suppress the aforementioned exception in the tomcat log? Including the Tomcat version helps ;-). I'm assuming that this is for the AJP/1.3 Connector. The answer is to change the logging level for that component to be one higher than the level in the message (in the latest version, it's at DEBUG level and I don't remember what it used to be). For example, if you are using JDK1.4 logging you would do something like: org.apache.jk.common.level=SEVERE in your logging.properties file. Thank you very much in advance, again! Dola __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Suppress Connection reset by peer: socket write error.
Hi, I apologize for asking this question again for I remembering asking this question in the past, but I can't find the response. What setting (and where) will suppress the aforementioned exception in the tomcat log? Thank you very much in advance, again! Dola __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connection Reset Problem
I recently upgraded from tomcat 4.1 to tomcat 5.0.25 and I am seeing the following in the stdout.log: Aug 8, 2005 11:50:43 PM org.apache.tomcat.util.net.TcpWorkerThread runIt SEVERE: Remote Host /XX.XXX.X.XXX SocketException: Connection reset Aug 8, 2005 11:50:43 PM org.apache.tomcat.util.net.TcpWorkerThread runIt SEVERE: Remote Host /XX.XXX.X.XXX SocketException: Connection reset Aug 8, 2005 11:50:43 PM org.apache.tomcat.util.net.TcpWorkerThread runIt SEVERE: Remote Host /XX.XXX.X.XXX SocketException: Connection reset Aug 8, 2005 11:50:43 PM org.apache.tomcat.util.net.TcpWorkerThread runIt SEVERE: Remote Host /XX.XXX.X.XXX SocketException: Connection reset Aug 8, 2005 11:50:43 PM org.apache.tomcat.util.net.TcpWorkerThread runIt SEVERE: Remote Host /XX.XXX.X.XXX SocketException: Connection reset there are many of these in the log. Any help would be greatly appreciated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connection reset by peer: socket write error
Hi, i´m in trouble with a Tomcat 4.1.29 (Standalone, no Apache !, Win2K) acting as as Mapserver. It seems to work fine, but writes tons of exceptions to isapi.log and sterr.log. I´ve googled a few hours withe the result, that 'Connection reset by peer' may happen when the client presses the stop button, closes connection etc. That is impossible, i´ve got over 1000 exceptions in my logfile. There must be another reason. isapi.log: [Thu Aug 04 14:44:27 2005] [jk_ajp_common.c (651)]: ajp_connection_tcp_get_message: Error - jk_tcp_socket_recvfull failed [Thu Aug 04 14:44:27 2005] [jk_ajp_common.c (1009)]: Error reading reply [Thu Aug 04 14:44:27 2005] [jk_ajp_common.c (1146)]: In jk_endpoint_t::service, ajp_get_reply failed in send loop 0 sterr.log: 04.08.2005 14:37:15 org.apache.jk.server.JkCoyoteHandler action SCHWERWIEGEND: Error in action code java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:457) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:654) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:435) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:314) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:615) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666) at java.lang.Thread.run(Thread.java:534) 04.08.2005 14:37:37 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached 04.08.2005 14:44:25 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached Maybe, someone can answer one of the following questions: - What is jk_ajp_common.c ? (Seems to be a native class for the Apache connector) - what is org.apache.jk.server.JkCoyoteHandler exacly responsible for ? - How do i know, what EXACT connection is reseted. - is the reseted connection necessarily a http connection or possibly a database connection ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error
Which line of code is on 71?
helloworldservlet.ServletVideo.streamBinaryData(ServletVideo.java:71)
In your finally block, you are closing the servlet output stream, I wonder if
that's causing tomcat a problem since it usually closes the servlet output
stream itself?
Humour me and change
if( outstr != null ) {
outstr.flush();
outstr.close();
}
to
if( outstr != null ) {
outstr.flush();
}
-Original Message-
From: Adriana Suarez [mailto:[EMAIL PROTECTED]
Sent: 28 June 2005 04:33
To: tomcat-user@jakarta.apache.org
Subject: ClientAbortException: java.net.SocketException: Connection
reset by peer: socket write error
Hello,
I got this exception and I don't know how to solve it, I have a web
application with a servlet which sends video with formats avi, mpeg,
and mov, it shows the video but the tomcat throws this exception:
ClientAbortException: java.net.SocketException: Connection reset by
peer: socket write error
at
org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBu
ffer.java:373)
at
org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:323)
at
org.apache.coyote.tomcat5.OutputBuffer.writeBytes(OutputBuffer
.java:401)
at
org.apache.coyote.tomcat5.OutputBuffer.write(OutputBuffer.java:388)
at
org.apache.coyote.tomcat5.CoyoteOutputStream.write(CoyoteOutpu
tStream.java:76)
at
java.io.BufferedOutputStream.write(BufferedOutputStream.java:106)
at
helloworldservlet.ServletVideo.streamBinaryData(ServletVideo.java:71)
at helloworldservlet.ServletVideo.doGet(ServletVideo.java:37)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilt
er(ApplicationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli
cationFilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardW
rapperValve.java:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Stand
ardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
ine.java:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(S
tandardContextValve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardC
ontextValve.java:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Stand
ardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
ine.java:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHost
Valve.java:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Stand
ardValveContext.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport
Valve.java:117)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Stand
ardValveContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
ine.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEn
gineValve.java:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Stand
ardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
ine.java:520)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.
java:160)
at
org.apache.coyote.http11.Http11Processor.process(Http11Process
or.java:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandle
r.processConnection(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoi
nt.java:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)
and this is where the code fails:
private void streamBinaryData(String urlstr,String
format,ServletOutputStream outstr, HttpServletResponse resp)
{
String ErrorStr = null;
try{
//find the right mime type and set it as contenttype
resp.setContentType(getMimeType(format));
BufferedInputStream bis = null;
BufferedOutputStream bos = null;
try{
URL url = new URL(urlstr);
URLConnection urlc= url.openConnection();
int length =urlc.getContentLength();
resp.setContentLength(length);
// Use Buffered Stream for reading/writing.
InputStream in = urlc.getInputStream();
bis = new BufferedInputStream(in);
bos = new BufferedOutputStream(outstr);
byte[] buff = new byte[length];
int bytesRead;
// Simple
RE: ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error
This exception means the client (browser) has closed the connection before
Tomcat send all its data. If the application works you should ignore this. My
log is full of it. It also happens if you download something large from Tomcat
and click cancel during the download.
Ronald.
On Tue Jun 28 10:04:14 CEST 2005 Tomcat Users List
tomcat-user@jakarta.apache.org wrote:
Which line of code is on 71?
helloworldservlet.ServletVideo.streamBinaryData(ServletVideo.java:71)
In your finally block, you are closing the servlet output stream, I wonder if that's causing tomcat a problem since it usually closes the servlet output stream itself?
Humour me and change
if( outstr != null ) {
outstr.flush();
outstr.close();
}
to
if( outstr != null ) {
outstr.flush();
}
-Original Message-
From: Adriana Suarez [mailto:[EMAIL PROTECTED]
Sent: 28 June 2005 04:33
To: tomcat-user@jakarta.apache.org
Subject: ClientAbortException: java.net.SocketException: Connection
reset by peer: socket write error
Hello,
I got this exception and I don't know how to solve it, I have a web
application with a servlet which sends video with formats avi, mpeg,
and mov, it shows the video but the tomcat throws this exception:
ClientAbortException: java.net.SocketException: Connection reset by
peer: socket write error
at
org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBu
ffer.java:373)
at
org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:323)
at
org.apache.coyote.tomcat5.OutputBuffer.writeBytes(OutputBuffer
.java:401)
at
org.apache.coyote.tomcat5.OutputBuffer.write(OutputBuffer.java:388)
at
org.apache.coyote.tomcat5.CoyoteOutputStream.write(CoyoteOutpu
tStream.java:76)
at
java.io.BufferedOutputStream.write(BufferedOutputStream.java:106)
at
helloworldservlet.ServletVideo.streamBinaryData(ServletVideo.java:71)
at helloworldservlet.ServletVideo.doGet(ServletVideo.java:37)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilt
er(ApplicationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli
cationFilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardW
rapperValve.java:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Stand
ardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
ine.java:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(S
tandardContextValve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardC
ontextValve.java:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Stand
ardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
ine.java:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHost
Valve.java:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Stand
ardValveContext.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport
Valve.java:117)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Stand
ardValveContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
ine.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEn
gineValve.java:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Stand
ardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
ine.java:520)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.
java:160)
at
org.apache.coyote.http11.Http11Processor.process(Http11Process
or.java:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandle
r.processConnection(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoi
nt.java:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)
and this is where the code fails:
private void streamBinaryData(String urlstr,String
format,ServletOutputStream outstr, HttpServletResponse resp)
{
String ErrorStr = null;
try{
//find the right mime type and set it as contenttype
resp.setContentType(getMimeType(format));
BufferedInputStream bis = null;
BufferedOutputStream bos = null;
try{
URL url = new URL(urlstr);
URLConnection urlc= url.openConnection();
int length =urlc.getContentLength();
resp.setContentLength(length);
// Use Buffered Stream for reading/writing.
InputStream in = urlc.getInputStream();
bis = new BufferedInputStream(in);
bos = new BufferedOutputStream(outstr);
byte[] buff = new byte[length];
int bytesRead;
// Simple read/write loop.
while(-1
Re: ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error
Connection reset by peer means the client disconnected before all the data was sent. -Tim Adriana Suarez wrote: Hello, I got this exception and I don't know how to solve it, I have a web application with a servlet which sends video with formats avi, mpeg, and mov, it shows the video but the tomcat throws this exception: ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error at org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:373) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error
Hello,
I got this exception and I don't know how to solve it, I have a web
application with a servlet which sends video with formats avi, mpeg,
and mov, it shows the video but the tomcat throws this exception:
ClientAbortException: java.net.SocketException: Connection reset by
peer: socket write error
at
org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:373)
at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:323)
at
org.apache.coyote.tomcat5.OutputBuffer.writeBytes(OutputBuffer.java:401)
at org.apache.coyote.tomcat5.OutputBuffer.write(OutputBuffer.java:388)
at
org.apache.coyote.tomcat5.CoyoteOutputStream.write(CoyoteOutputStream.java:76)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:106)
at helloworldservlet.ServletVideo.streamBinaryData(ServletVideo.java:71)
at helloworldservlet.ServletVideo.doGet(ServletVideo.java:37)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)
and this is where the code fails:
private void streamBinaryData(String urlstr,String
format,ServletOutputStream outstr, HttpServletResponse resp)
{
String ErrorStr = null;
try{
//find the right mime type and set it as contenttype
resp.setContentType(getMimeType(format));
BufferedInputStream bis = null;
BufferedOutputStream bos = null;
try{
URL url = new URL(urlstr);
URLConnection urlc= url.openConnection();
int length =urlc.getContentLength();
resp.setContentLength(length);
// Use Buffered Stream for reading/writing.
InputStream in = urlc.getInputStream();
bis = new BufferedInputStream(in);
bos = new BufferedOutputStream(outstr);
byte[] buff = new byte[length];
int bytesRead;
// Simple read/write loop.
while(-1 != (bytesRead = bis.read(buff, 0, buff.length))) {
bos.write(buff, 0, bytesRead);
}
} catch (Exception e) {
e.printStackTrace();
ErrorStr = Error Streaming the Data;
outstr.print(ErrorStr);
} finally {
if( bis != null ) {
bis.close();
}
if( bos != null ) {
bos.close();
}
if( outstr != null ) {
outstr.flush();
outstr.close();
}
}
}
catch(Exception e){
e.printStackTrace();
}
}
I have
ClientAbortException... Connection reset after 496ko
Hello all, I'm using Tomcat 5.5.9, apache_2.0.54 and Jakarta Tomcat Connectors 1.2.13 on a red hat enterprise v4 server. I can't even download a zip file from the web server, it fails after 496ko every time. In the catalina.out I see org.apache.jk.common.ChannelSocket processConnection WARNING: processCallbacks status 2 and in the Apache errors.log [notice] child pid 11143 exit signal Segmentation fault (11) If I have a servlet writing the datas to the outputStream I can catch the following IOException exception : ClientAbortException: java.net.SocketException: Connection reset at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:366) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:403) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:323) at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:392) at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:381) at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:76) at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:70) On the client side, I see (with wget) Connection closed at byte 507,904 The weird thing, is that if I go directly to Tomcat it works : ie: http://myserver:8080/mywebapp/file.zip works fine. while http://myserver/mywebapp/file.zip fails after 496ko. I can't connect directly to Tomcat, as I need to have several load-balanced servers, but I took this out to try to isolate the problem. I don't know where to look anymore, any ideas ? thanks for your time Have a nice day Lucho - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AutoReply: ClientAbortException... Connection reset after 496ko
***This is an auto generated mail, to aknowledge the receiept of your mail*** Hello tomcat-user@jakarta.apache.org, This refers to your mail with subject ClientAbortException... Connection reset after 496ko receieved on Thu, 23 Jun 2005 18:23:16 GMT from Luc Giavelli [EMAIL PROTECTED] to our email id - [EMAIL PROTECTED] Thank you for applying for the advertised position with one of our leading clients. We will contact you by phone/email, if we find your profile meeting the client's requirement. In case you require any further information please do contact us. with warm regards, Team @ A. S. Consultancy Services #1205, 2nd Main, 2nd Cross, Vijayanagar, Bangalore - 560040, India Tele - 91 80 2310 9012, Telefax - 91 80 2330 5364, Email: [EMAIL PROTECTED] URL: www.asconsultancy.com Please Note 1. This email id (tomcat-user@jakarta.apache.org) is meant for receiving job application mails only. For other informartion, please contact us at the above mentioned contact details. 2. This message and any files transmitted with it contain confidential information and are intended only for the individual named. If you are not the named addressee you must not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. 3. E-mail transmission cannot be guaranteed to be fully or partly secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The recipient should check this email and any attachments for the presence of viruses. The sender neither accepts liability for any errors or omissions in the contents of this message nor accepts any liability for any damage caused by any virus, which arise as a result of e-mail transmission. Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connection reset by peer: socket write error
Hi, When a page is loading -- it is a page with large ammount of data from database, I clicked a button. I see the exception on the monitor window: Connection reset by peer: socket write error. The detal error is attached. This message might be harmless. I think it is because the response has not finished the task. Is there a way to know the response is finished and the socket is idle? Anybody has some suggestion? Any setting in tomcat? Thanks. Mar 2, 2005 5:09:11 PM org.apache.jk.server.JkCoyoteHandler action SEVERE: Error in action code java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:489) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:697) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:487) at org.apache.coyote.Response.action(Response.java:226) at org.apache.coyote.Response.finish(Response.java:348) at org.apache.coyote.tomcat5.OutputBuffer.close(OutputBuffer.java:328) at org.apache.coyote.tomcat5.CoyoteResponse.finishResponse(CoyoteResponse.java: 497) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:209) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:339) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:415) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:716) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:650) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:829) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:688) at java.lang.Thread.run(Thread.java:534) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connection reset by peer: socket write error
Hi, I get these all the time. They don't seem to be disruptive so I don't worry about them too much. But the do obscure the valuable output so I would like to eliminate them if psiible. Dola ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:365) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:403) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:313) at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:292) at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:85) at universe.Chartable$PertracStylePerformance.pOutputChart(Chartable.java:226) at servlets.ChartGenerator.doGet(ChartGenerator.java:25) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) 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:825) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:731) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526) 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:534) __ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connection reset by peer: socket write error
I get those frequently as well, but only in one or two specific places. I've actually factored them out of my code (i.e., if they are thrown, I ignore them instead of allowing them to be logged). As you said, not disruptive, just clogging up the logs. As near as I've been able to figure out, they occur when a user clicks stop, or the browser times out, usually it only seems to occur when your streaming something to the response object, like a PDF for instance. I too would like to know for sure what causes them, but this is what seems to be the cause. -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Tue, January 25, 2005 2:16 pm, Dola Woolfe said: Hi, I get these all the time. They don't seem to be disruptive so I don't worry about them too much. But the do obscure the valuable output so I would like to eliminate them if psiible. Dola ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:365) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:403) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:313) at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:292) at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:85) at universe.Chartable$PertracStylePerformance.pOutputChart(Chartable.java:226) at servlets.ChartGenerator.doGet(ChartGenerator.java:25) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) 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:825) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:731) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526) 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:534) __ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connection reset by peer: socket write error
Dola Woolfe wrote: Hi, I get these all the time. This exception occurs when a client made a request, and before receiving the full response, either of the following happened: 1. client's browser has been closed. 2. client's connection has been disconnected. 3. client presses the stop button. They don't seem to be disruptive so I don't worry about them too much. But the do obscure the valuable output so I would like to eliminate them if psiible. Also when describing a problem it would be a valuable to mention at least the Tomcat version and possibly the OS you are using. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connection reset by peer: socket write error
Is there a way to suppress them? I'm using TC5.5.4 on XP. --- Mladen Turk [EMAIL PROTECTED] wrote: Dola Woolfe wrote: Hi, I get these all the time. This exception occurs when a client made a request, and before receiving the full response, either of the following happened: 1. client's browser has been closed. 2. client's connection has been disconnected. 3. client presses the stop button. They don't seem to be disruptive so I don't worry about them too much. But the do obscure the valuable output so I would like to eliminate them if psiible. Also when describing a problem it would be a valuable to mention at least the Tomcat version and possibly the OS you are using. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connection reset by peer: socket write error
Dola Woolfe wrote: Is there a way to suppress them? I'm using TC5.5.4 on XP. Do not use debug log level. Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connection reset by peer: socket write error
Do not use debug log level. Mladen. Is it this part of of web.xml and should the 6 be lowered? servlet servlet-namecgi/servlet-name servlet-classorg.apache.catalina.servlets.CGIServlet/servlet-class init-param param-namedebug/param-name param-value6/param-value /init-param init-param param-namecgiPathPrefix/param-name param-valueWEB-INF/cgi/param-value /init-param load-on-startup5/load-on-startup /servlet __ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SocketException: Connection reset - Tomcat 5.0.27
When using Tomcat 5.0.27 the following error shows up in the catalina.log file; SEVERE: Remote Host 12.159.66.150 SocketException: Connection reset org.apache.tomcat.util.net.TcpWorkerThread runIt The ip address 12.159.66.150 is a load balancer that front-ends Tomcat and checks periodically to make sure tomcat is running. It logs this error every time it checks. When I switch to Tomcat 5.0.16 under the same exact conditions this error does not show up in the log file. Questions; Is there a way to prevent this from being logged? Why does this occur under Tomcat 5.0.27 and not Tomcat 5.0.16? If Tomcat cant be set up to not log this error, is there a way to log in as INFO instead? alan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SEVERE: Remote Host 12.159.66.150 SocketException: Connection reset
When using Tomcat 5.0.27 the following error shows up in the catalina.log file; SEVERE: Remote Host 12.159.66.150 SocketException: Connection reset org.apache.tomcat.util.net.TcpWorkerThread runIt The ip address 12.159.66.150 is a load balancer that front-ends Tomcat and checks every 5 secs to make sure tomcat is running (by checking the port tomcat runs on). When I switch to Tomcat 5.0.16 under the same exact conditions this does not show up in the log file. It does not hurt the performance of Tomcat but it is causing a huge and unreadable log file, and in addition, we monitor the log files for SEVERE errors and send out an email when any occur Questions; What exactly does this mean? (I believe it to mean a client closed the connection to tomcat before tomcat had a chance to reply to it.) Is there a way to prevent this from being logged? Why does this occur under Tomcat 5.0.27 and not Tomcat 5.0.16? If Tomcat cant be set up to not log this error, is there a way to log in as INFO instead?
Problem with tomcat 4.1.24 : java.net.SocketException: Connection reset by peer: socket write error
Hi All I get the following error and my webserver gets hung up. After restarting the server everything works fine for a while until hangs up again. Using Tomcat 4.1.24. Help needed desperately. StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.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$OutputStreamOutputBuffer.d oWrite(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOu tputFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuff er.java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java: 384) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:439) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:359) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.ja va:110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.jav a:1996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:174 5) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet .java:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:50 6) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.ja va:246) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241 5) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa lve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:59 4) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC onnection(Http11Protocol.java:392
Connection reset by peer: socket write error(CODE=-1)
Hello, For some reason when i use tomcat 's (4.1.30 ) jndi pooling with MSSQL, i get this error. Connection reset by peer: socket write error(CODE=-1) I suspect that the problem is with the fact that connections go stale. is there a way for me to force connection to be renewed, or for connection pooling to check if connection is stale? alex k. Resource auth=Container name=jdbc/WBTPCDataSource scope=Shareable type=javax.sql.DataSource/ ResourceParams name=jdbc/WBTPCDataSource parameter namemaxWait/name value5000/value /parameter parameter namemaxActive/name value10/value /parameter parameter namedriverName/name valuejdbc:microsoft:sqlserver/value /parameter parameter nameurl/name valuejdbc:microsoft:sqlserver://localhost:1433;DatabaseName=WB_TPC;SelectMethod=Cursor/value /parameter parameter namepassword/name valuepassword/value /parameter parameter namedriverClassName/name valuecom.microsoft.jdbc.sqlserver.SQLServerDriver/value /parameter parameter namemaxIdle/name value2/value /parameter parameter nameusername/name valueuser/value /parameter parameter nameremoveAbandoned/name valuetrue/value /parameter parameter nameremoveAbandonedTimeout/name value2/value /parameter parameter namelogAbandoned/name valuetrue/value /parameter /ResourceParams - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Native application from servlet (java.net.SocketException: Connection reset by peer: socket write error)
Hi all, We have a servlet based application which open a native application and read some output from them. Sometimes we get an error in tomcat logfile but application work fine. Here is error. Any ideas what is possible problem? 2004-02-09 10:02:26 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.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$OutputStreamOutputBuffer.d oWrite(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOu tputFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuff er.java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java: 384) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:439) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:359) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.ja va:110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.jav a:1996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:174 5) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet .java:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:50 6) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticator Base.java:494) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241 5) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa lve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:59 4) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC onnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:56 5) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:619) at java.lang.Thread.run(Thread.java:536) Veso
Re: Native application from servlet (java.net.SocketException: Connection reset by peer: socket write error)
Veselin Kovacevic wrote, On 2/10/2004 2:14 AM: We have a servlet based application which open a native application and read some output from them. Sometimes we get an error in tomcat logfile but application work fine. Here is error. Any ideas what is possible problem? Looks normal. Appears to be that someone pushed stopped in their browser which closed Tomcat's output stream to the user. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Open native console application from servlet (java.net.SocketException: Connection reset by peer: socket write error)
Hi all, We have a servlet based application which open a native console application and read samo output from them. Sometimes we get an error in tomcat logfile but application work ok. What is happen? Here is error. What is mean? 2004-02-09 10:02:26 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.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$OutputStreamOutputBuffer.d oWrite(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOu tputFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuff er.java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java: 384) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:439) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:359) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.ja va:110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.jav a:1996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:174 5) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet .java:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:50 6) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticator Base.java:494) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241 5) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa lve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:59 4) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC onnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:56 5) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:619) at java.lang.Thread.run(Thread.java:536)
java.net.SocketException: Connection reset
Hello, list. I've installed Tomcat 4.1.24 and MySQL 4.0.16 and tomcat and a aplication that access to the data base with a heavy load. crash sometimes per day and I've seen the next error in the tomcat log: 2004-01-13 08:13:48 StandardHost[localhost]: MAPPING configuration error for request URI /opencms/export/eintranet/index.html 2004-01-13 08:20:16 StandardHost[localhost]: MAPPING configuration error for request URI /opencms/export/eintranet/index.html StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.net.SocketException: Connection reset. 2004-01-13 08:13:48 StandardHost[localhost]: MAPPING configuration error for request URI /opencms/export/eintranet/index.html 2004-01-13 08:20:16 StandardHost[localhost]: MAPPING configuration error for request URI /opencms/export/eintranet/index.html Any idea how to solve this or What could be the cause of this problem? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
java.net.SocketException: Connection reset
Hello, list. I've installed Tomcat 4.1.24 and MySQL 4.0.16 and tomcat and a aplication that access to the data base with a heavy load. crash sometimes per day and I've seen the next error in the tomcat log: 2004-01-13 08:13:48 StandardHost[localhost]: MAPPING configuration error for request URI /opencms/export/eintranet/index.html 2004-01-13 08:20:16 StandardHost[localhost]: MAPPING configuration error for request URI /opencms/export/eintranet/index.html StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.net.SocketException: Connection reset. 2004-01-13 08:13:48 StandardHost[localhost]: MAPPING configuration error for request URI /opencms/export/eintranet/index.html 2004-01-13 08:20:16 StandardHost[localhost]: MAPPING configuration error for request URI /opencms/export/eintranet/index.html Any idea how to solve this or What could be the cause of this problem? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat: Connection reset by peer: socket write error
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5735 http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4663 -Original Message- From: Boemio, Neil (IT, FGIC) [mailto:[EMAIL PROTECTED] Sent: 07 2004 . 22:16 To: Tomcat Users List Subject: Tomcat: Connection reset by peer: socket write error My W2K, Apache 2.0.47, Tomcat 4.1.27, JK2 2.0.43 setup works fine . for a while. After an hour, a few hours, maybe minutes (I don't really see a pattern), my JSP pages will hang. When I restart the Tomcat service, everything is fine again until the next hang. Here's the sequence: About every minute in the jk2.log, I get this set or errors over and over again. This doesn't seem to be directly related to my problem because this happens even when everything is OK but I thought I would include it as well: [Wed Jan 07 14:19:27 2004] (error ) [jk_channel_socket.c (557)] channelSocket.receive(): Error receiving message body -1 0 [Wed Jan 07 14:19:27 2004] (error ) [jk_workerEnv.c (482)] workerEnv.processCallbacks() Error reading reply [Wed Jan 07 14:19:27 2004] (error ) [jk_worker_ajp13.c (416)] ajp13.service() ajpGetReply recoverable error 12 [Wed Jan 07 14:19:49 2004] (error ) [jk_channel_socket.c (557)] channelSocket.receive(): Error receiving message body -1 0 [Wed Jan 07 14:19:49 2004] (error ) [jk_workerEnv.c (482)] workerEnv.processCallbacks() Error reading reply [Wed Jan 07 14:19:49 2004] (error ) [jk_worker_ajp13.c (416)] ajp13.service() ajpGetReply recoverable error 12 When the problem occurs, I get this in the Tomcat Error Log: Jan 7, 2004 2:21:25 PM org.apache.jk.server.JkCoyoteHandler action SEVERE: Error in action code java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown Source) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:599) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:385) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:268) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:604) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSo cket.java:562) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( ThreadPool.java:619) at java.lang.Thread.run(Unknown Source) Then at about the same time as the error, I get this in the jk2.log: [Wed Jan 07 14:21:25 2004] (error ) [jk_handler_response.c (200)] Error ajp_process_callback - write failed [Wed Jan 07 14:21:25 2004] (error ) [jk_worker_ajp13.c (416)] ajp13.service() ajpGetReply recoverable error 3 [Wed Jan 07 14:21:25 2004] (error ) [jk_handler_response.c (200)] Error ajp_process_callback - write failed [Wed Jan 07 14:21:25 2004] (error ) [jk_worker_ajp13.c (416)] ajp13.service() ajpGetReply recoverable error 3 [Wed Jan 07 14:21:25 2004] (error ) [jk_worker_ajp13.c (512)] ajp13.service() Error forwarding ajp13:localhost:8009 1 0 [Wed Jan 07 14:21:25 2004] (error ) [mod_jk2.c (678)] mod_jk.handler() Error connecting to tomcat 3 Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat: Connection reset by peer: socket write error
My W2K, Apache 2.0.47, Tomcat 4.1.27, JK2 2.0.43 setup works fine . for a while. After an hour, a few hours, maybe minutes (I don't really see a pattern), my JSP pages will hang. When I restart the Tomcat service, everything is fine again until the next hang. Here's the sequence: About every minute in the jk2.log, I get this set or errors over and over again. This doesn't seem to be directly related to my problem because this happens even when everything is OK but I thought I would include it as well: [Wed Jan 07 14:19:27 2004] (error ) [jk_channel_socket.c (557)] channelSocket.receive(): Error receiving message body -1 0 [Wed Jan 07 14:19:27 2004] (error ) [jk_workerEnv.c (482)] workerEnv.processCallbacks() Error reading reply [Wed Jan 07 14:19:27 2004] (error ) [jk_worker_ajp13.c (416)] ajp13.service() ajpGetReply recoverable error 12 [Wed Jan 07 14:19:49 2004] (error ) [jk_channel_socket.c (557)] channelSocket.receive(): Error receiving message body -1 0 [Wed Jan 07 14:19:49 2004] (error ) [jk_workerEnv.c (482)] workerEnv.processCallbacks() Error reading reply [Wed Jan 07 14:19:49 2004] (error ) [jk_worker_ajp13.c (416)] ajp13.service() ajpGetReply recoverable error 12 When the problem occurs, I get this in the Tomcat Error Log: Jan 7, 2004 2:21:25 PM org.apache.jk.server.JkCoyoteHandler action SEVERE: Error in action code java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown Source) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:599) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:385) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:268) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:604) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:562) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Unknown Source) Then at about the same time as the error, I get this in the jk2.log: [Wed Jan 07 14:21:25 2004] (error ) [jk_handler_response.c (200)] Error ajp_process_callback - write failed [Wed Jan 07 14:21:25 2004] (error ) [jk_worker_ajp13.c (416)] ajp13.service() ajpGetReply recoverable error 3 [Wed Jan 07 14:21:25 2004] (error ) [jk_handler_response.c (200)] Error ajp_process_callback - write failed [Wed Jan 07 14:21:25 2004] (error ) [jk_worker_ajp13.c (416)] ajp13.service() ajpGetReply recoverable error 3 [Wed Jan 07 14:21:25 2004] (error ) [jk_worker_ajp13.c (512)] ajp13.service() Error forwarding ajp13:localhost:8009 1 0 [Wed Jan 07 14:21:25 2004] (error ) [mod_jk2.c (678)] mod_jk.handler() Error connecting to tomcat 3 Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connection Reset By Peer
Can someone please explain to me what does Connection reset by peer means? Does it mean the server does not recognize the connection attempt from Tomcat or are there some other explanations. Or is there some port not available...:-(. 2003-12-17 01:14:06 - ContextManager: SocketException reading request, ignored - java.net.SocketException: Connection reset by peer at java.net.PlainSocketImpl.socketAvailable(Native Method) at java.net.PlainSocketImpl.available(PlainSocketImpl.java:501) at java.net.SocketInputStream.available(SocketInputStream.java:142) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC onnectionHandler.java:217) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) at java.lang.Thread.run(Thread.java:479) Thanx. André Ferreira Note: The information in this e-mail is confidential and is intended solely for the addressee. If you have received this e-mail in error, you are hereby notified that any review, copying or distribution is strictly prohibited. Please inform the sender immediately and destroy the original. Siemens Limited and/or its subsidiaries accepts no liability of whatever nature for any loss, liability, damage or expense resulting directly or indirectly from access to this message and any files or links that are attached hereto.
Re: Connection Reset By Peer
Hi! Ferreira, André wrote: Can someone please explain to me what does Connection reset by peer means? Does it mean the server does not recognize the connection attempt from Tomcat or are there some other explanations. Or is there some port not available...:-(. Since TCP is a connection-less protocol, it uses a three-way handshake to simulate a connection. The client sends a packet with only the SYN bit set, the server replies with a SYN ACK packet and the client acknowledges this with a single ACK. After that, server and client have agreed to act as if they were actually connected to each other and they begin to actually exchange data. If now at any time one of the two sends a packet with the RST (reset) bit set, this indicates that the makeshift connection has been disrupted. This can have many reasons. So, connection reset by peer on one end (e.g. the broswer) means, that the other end (in this case the server) closed the connection for reasons unknown. In this case, the server process is running fine and the port is available as well, the server just wouldn't talk to you. Phil -- And on the seventh day, He exited from append mode. (Book of create(2), line 255) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connection Reset
Here is our architecture. 5 web servers (web1 - web5) and 4 java servers (java4-java7) Each Webserver is using the same version of mod_jk (version 1.2.5) and apache (1.3.27). Each java server is running the same version of tomcat (3.3.1a). Red Hat is being used on both web servers and java servers. When we have mod_jk load balancing turned on (see config at url below) the following errors (see http://titan.cbc.ca/~bcrosby/tomcat.txt) in tomcat.err are present. On the webserver, the mod_jk error file shows: [Tue Dec 16 18:18:27 2003] [jk_ajp_common.c (1303)]: ERROR: Client connection aborted or network problems Turning mod_jk load balancing off fixes this problem. A copy of the workers.properties file is available at http://titan.cbc.ca/~bcrosby/workers.txt. Questions: 1. What is the definition of client according to mod_jk. In the error message from mod_jk (see above) client connection aborted means tomcat aborted the connection (tomcat being the client) or apache/mod_jk aborted the connection. 2. Are there any values (like socket_keepalive) that are missing in my workers.properties file? Let me know if you need any more info. -- Blake Crosby - CBC.ca Operations Platform Administrator voice://+1.416.205.3103 mobile://+1.416.884.5828 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Connection Reset
Blake Crosby [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Here is our architecture. 5 web servers (web1 - web5) and 4 java servers (java4-java7) Each Webserver is using the same version of mod_jk (version 1.2.5) and apache (1.3.27). Each java server is running the same version of tomcat (3.3.1a). Red Hat is being used on both web servers and java servers. When we have mod_jk load balancing turned on (see config at url below) the following errors (see http://titan.cbc.ca/~bcrosby/tomcat.txt) in tomcat.err are present. On the webserver, the mod_jk error file shows: [Tue Dec 16 18:18:27 2003] [jk_ajp_common.c (1303)]: ERROR: Client connection aborted or network problems Turning mod_jk load balancing off fixes this problem. A copy of the workers.properties file is available at http://titan.cbc.ca/~bcrosby/workers.txt. Questions: 1. What is the definition of client according to mod_jk. In the error message from mod_jk (see above) client connection aborted means tomcat aborted the connection (tomcat being the client) or apache/mod_jk aborted the connection. Client means the browser. The message usually means that e.g. the user hit the stop button. However, in this case it looks like a problem with the load-balancer. At least that's what a quick look at the code suggests. 2. Are there any values (like socket_keepalive) that are missing in my workers.properties file? KeepAlive shouldn't matter much. Let me know if you need any more info. -- Blake Crosby - CBC.ca Operations Platform Administrator voice://+1.416.205.3103 mobile://+1.416.884.5828 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connection reset
Hi everyone, I am running tomcat 4 on Red Hat Linux 8. Although my web application seems to be running ok, when i look at the localhost_log, i find the following stack trace. It seems to happen a few times everyday. Also, a very small number of users get a 'Page not Found' when they try accessing my application, and for some others they get the initial login page, but when they enter their ID and Pwd and hit submit, tomcat doesnt seem to recognise their session. I am using session cookies and not url rewriting. I have SSL set up on tomcat (i created my own certificate using keytool) and my users are using https to connect to the web application. If anyone has encountered the problem before, or have suggestions for me, that would be very helpful. The stack trace is below. I dont know if it is related to some users not being able to access the application, or if it is something else. 2003-09-25 10:31:11 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.net.SocketException: Connection reset at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at com.sun.net.ssl.internal.ssl.OutputRecord.a(DashoA6275) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(DashoA6275) at org.apache.catalina.connector.ResponseBase.flushBuffer(ResponseBase.java:675) at org.apache.catalina.connector.HttpResponseBase.doFlushBuffer(HttpResponseBase.java:795) at org.apache.catalina.connector.HttpResponseBase.flushBuffer(HttpResponseBase.java:785) at org.apache.catalina.connector.ResponseBase.write(ResponseBase.java:648) at org.apache.catalina.connector.ResponseStream.write(ResponseStream.java:313) at org.apache.catalina.connector.http.HttpResponseStream.write(HttpResponseStream.java:190) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.java:1996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:1745) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:506) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995
RE: Connection reset by peer: socket write error in tomcat log
I think a lot of people have lots of these entries. :) Here's my idea: What it means is that the client (your browser) has closed the tcp/ip connection between itself and Tomcat, before Tomcat thinks it is done sending data. Since the images and pages seem to be 100% complete (because you don't mention that you are experiencing any actual page load problems), one could wonder whether or not Tomcat is correct, but putting that aside... the problem is not Tomcat related, so much as it is connection related. The 'solution' is to simply disable this message. In Tomcat 3.2.x, go to TOMCAT_HOME/conf/server.xml and modify the following: code: - Logger name=tc_log verbosityLevel = INFORMATION - Change INFORMATION to WARNING, and that particular message should no longer appear. You will still get all the error stack traces, but none of the 'information' messages. I haven't found how to set this in Tomcat 4.x. Can someone else help us out on that one? -Original Message- From: Jiang Chen [mailto:[EMAIL PROTECTED] Sent: Friday, September 05, 2003 11:35 PM To: Tomcat Users List Subject: Connection reset by peer: socket write error in tomcat log Hi; I have quite a lot following exception in the tomcat log: ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/pages/error.jsp] java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutp utBuffer.doWri te(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(C hunkedOutputFi lter.java:171) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(Internal OutputBuffer.j ava:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBu ffer.java:384) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.coyote.tomcat4.OutputBuffer.flush(OutputBuffer.java:345) at org.apache.coyote.tomcat4.CoyoteResponse.flushBuffer(CoyoteRes ponse.java:555 ) at org.apache.coyote.tomcat4.CoyoteResponseFacade.flushBuffer(Coy oteResponseFac ade.java:227) at org.apache.catalina.valves.ErrorDispatcherValve.status(ErrorDi spatcherValve. java:307) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDi spatcherValve. java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValv eContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport Valve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValv eContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipel ine.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEn gineValve.java :174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValv eContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipel ine.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter. java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Process or.java:432) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandle r.processConne ction(Http11Protocol.java:386) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoi nt.java:534) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( ThreadPool.jav a:530) at java.lang.Thread.run(Thread.java:479) I am using Tomcat 4.1.18 and Structs 1.0, running at w2k box. Does anyone know what cause it, and how to fix it? Thanks a lot Jiang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connection reset by peer: socket write error in tomcat log
Hi; I have quite a lot following exception in the tomcat log: ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/pages/error.jsp] java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:91) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWri te(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFi lter.java:171) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.j ava:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java:384) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:360) at org.apache.coyote.tomcat4.OutputBuffer.flush(OutputBuffer.java:345) at org.apache.coyote.tomcat4.CoyoteResponse.flushBuffer(CoyoteResponse.java:555 ) at org.apache.coyote.tomcat4.CoyoteResponseFacade.flushBuffer(CoyoteResponseFac ade.java:227) at org.apache.catalina.valves.ErrorDispatcherValve.status(ErrorDispatcherValve. java:307) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:386) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:530) at java.lang.Thread.run(Thread.java:479) I am using Tomcat 4.1.18 and Structs 1.0, running at w2k box. Does anyone know what cause it, and how to fix it? Thanks a lot Jiang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connection reset by peer
I've spent some time searching for an answer to this one - several users have asked the question, but I can't find an answer. Apologies if it's been asked many times before. I have managed to get the Address Book SOAP example for work fine, but when I try to run an example that requires the server to access a web site to retrieve some information to be sent to the client I get the following error message: [SOAPException: faultCode=SOAP-ENV:Client; msg=Connection reset by peer: JVM_recv in socket input stream read; targetException=java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read] at org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnectio n.java:328) and so on. I would be very grateful if someone could suggest a solution, as I have spent days trying to get this example to work. Thanks, David Etheridge Technology Innovation Centre University of Central England Birmingham UK
java.net.SocketException: Connection reset
Hello, I am getting the java.net.SocketException and my JSP application crashes. I have pasted the exception below. It comes from the catalina sockets engine. Does anyone have an idea where should I go further for fixing this socket problem? My server configuration: Redhat Linux, Tomcat 4.1.24, Java 1.4.1 2003-06-09 12:24:38 StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.net.SocketException: Connection reset at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutputFilter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java:384) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:439) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:359) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411) at org.apache.coyote.tomcat4.OutputBuffer.write(OutputBuffer.java:398) at org.apache.coyote.tomcat4.CoyoteOutputStream.write(CoyoteOutputStream.java:110) at org.apache.catalina.servlets.DefaultServlet.copyRange(DefaultServlet.java:1996) at org.apache.catalina.servlets.DefaultServlet.copy(DefaultServlet.java:1745) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:1073) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:506) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:536) Thanks, -- Kaunas Regional Distance Education Center Programmer Phone: +370 674 05232 WWW: http://distance.ktu.lt
RE: IO Exception: Connection reset by peer: socket write error
Sounds like some sort of timeout or firewall blocking to me. If it works fine when both nodes are on a local network or subnet, but not when they are remote, something in-between is causing problems, or one or the other nodes is not set to wait long enough for delays caused by intervening networks or routers. John -Original Message- From: Lior Shliechkorn [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 4:56 PM To: Tomcat Users List Subject: RE: IO Exception: Connection reset by peer: socket write error Agreed on that one. However, back to the issue, this is not letting me log back in to the application. And, it's not throwing an exception in the filter that I have that gets/releases DB connections from a connection pool. When the application is run over in the same network as the DB there is no problem at all. Just when I run it from a different location it seems to act up in this manner. That's why I'm not quite sure. Turner, John [EMAIL PROTECTED] wrote: Never mind...I missed the part about the DB. *sigh* ...time for an after work beer. John -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: IO Exception: Connection reset by peer: socket write error
Thanks John. That sounds like the most likely scenario. Turner, John [EMAIL PROTECTED] wrote: Sounds like some sort of timeout or firewall blocking to me. If it works fine when both nodes are on a local network or subnet, but not when they are remote, something in-between is causing problems, or one or the other nodes is not set to wait long enough for delays caused by intervening networks or routers. John -Original Message- From: Lior Shliechkorn [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 4:56 PM To: Tomcat Users List Subject: RE: IO Exception: Connection reset by peer: socket write error Agreed on that one. However, back to the issue, this is not letting me log back in to the application. And, it's not throwing an exception in the filter that I have that gets/releases DB connections from a connection pool. When the application is run over in the same network as the DB there is no problem at all. Just when I run it from a different location it seems to act up in this manner. That's why I'm not quite sure. Turner, John wrote: Never mind...I missed the part about the DB. *sigh* ...time for an after work beer. John -- To unsubscribe, e-mail: For additional commands, e-mail: - Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
IO Exception: Connection reset by peer: socket write error
Hi, I'm running an app from a remote location (Chicago) with a database located in New York. I know this is not by any means a recommended practice, however, it's for testing purposes. My question is why this is occuring? The application works fine, but if I try to access it after a little time has passed I get that exception thrown. What is the issue? How can I solve this? Thank you very much, Lior - Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
RE: IO Exception: Connection reset by peer: socket write error
Howdy, You're going to need to give us a lot more than that ;) What tomcat version, what connectors, full stack trace / log if possible, etc... ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Lior Shliechkorn [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 4:38 PM To: Tomcat Subject: IO Exception: Connection reset by peer: socket write error Hi, I'm running an app from a remote location (Chicago) with a database located in New York. I know this is not by any means a recommended practice, however, it's for testing purposes. My question is why this is occuring? The application works fine, but if I try to access it after a little time has passed I get that exception thrown. What is the issue? How can I solve this? Thank you very much, Lior - Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: IO Exception: Connection reset by peer: socket write error
On Thu, 16 Jan 2003 10:37, Lior Shliechkorn wrote: Hi, I'm running an app from a remote location (Chicago) with a database located in New York. I know this is not by any means a recommended practice, however, it's for testing purposes. My question is why this is occuring? The application works fine, but if I try to access it after a little time has passed I get that exception thrown. A wild guess might be that the connection is being reset by the DB after a peiod of non-use, which throws an IO Exception the next time the DB is accessed by the web app. Usually a SQL exception would be thrown however, so don't treat this suggestion as gospel. I know at least two databases which have this behaviour (Postgres, and some versions of Interbase). Regards, Peter -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: IO Exception: Connection reset by peer: socket write error
Right, sorry. Tomcat 4.0.5, using ajp13 connectors. This is a catalina log output for the error: 2003-01-15 08:05:54 HttpProcessor[8080][3] process.parse java.io.IOException: Couldn't read line at org.apache.catalina.connector.http.SocketInputStream.readRequestLine(SocketInputStream.java:235) at org.apache.catalina.connector.http.HttpProcessor.parseRequest(HttpProcessor.java:710) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:974) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125) at java.lang.Thread.run(Thread.java:479) This is the apache log file error: 2003-01-15 07:31:41 [org.apache.catalina.connector.warp.WarpConnector] Error accepting requests java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463) at java.net.ServerSocket.implAccept(ServerSocket.java:238) at java.net.ServerSocket.accept(ServerSocket.java:217) at org.apache.catalina.connector.warp.WarpConnector.run(WarpConnector.java:590) at java.lang.Thread.run(Thread.java:479) Am I missing anything else...? Thanks Shapira, Yoav [EMAIL PROTECTED] wrote:Howdy, You're going to need to give us a lot more than that ;) What tomcat version, what connectors, full stack trace / log if possible, etc... ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Lior Shliechkorn [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 4:38 PM To: Tomcat Subject: IO Exception: Connection reset by peer: socket write error Hi, I'm running an app from a remote location (Chicago) with a database located in New York. I know this is not by any means a recommended practice, however, it's for testing purposes. My question is why this is occuring? The application works fine, but if I try to access it after a little time has passed I get that exception thrown. What is the issue? How can I solve this? Thank you very much, Lior - Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now -- To unsubscribe, e-mail: For additional commands, e-mail: - Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
RE: IO Exception: Connection reset by peer: socket write error
Agreed, though in my experience connection reset by peer messages mean the browser/client has stopped accepting data from the server, for various reasons: timeouts, closing the browser window, etc. In most situations, they are harmless. John -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 4:41 PM To: Tomcat Users List Subject: RE: IO Exception: Connection reset by peer: socket write error Howdy, You're going to need to give us a lot more than that ;) What tomcat version, what connectors, full stack trace / log if possible, etc... ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Lior Shliechkorn [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 4:38 PM To: Tomcat Subject: IO Exception: Connection reset by peer: socket write error Hi, I'm running an app from a remote location (Chicago) with a database located in New York. I know this is not by any means a recommended practice, however, it's for testing purposes. My question is why this is occuring? The application works fine, but if I try to access it after a little time has passed I get that exception thrown. What is the issue? How can I solve this? Thank you very much, Lior - Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: IO Exception: Connection reset by peer: socket write error
Never mind...I missed the part about the DB. *sigh* ...time for an after work beer. John -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 4:45 PM To: 'Tomcat Users List' Subject: RE: IO Exception: Connection reset by peer: socket write error Agreed, though in my experience connection reset by peer messages mean the browser/client has stopped accepting data from the server, for various reasons: timeouts, closing the browser window, etc. In most situations, they are harmless. John -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 4:41 PM To: Tomcat Users List Subject: RE: IO Exception: Connection reset by peer: socket write error Howdy, You're going to need to give us a lot more than that ;) What tomcat version, what connectors, full stack trace / log if possible, etc... ;) Yoav Shapira Millennium ChemInformatics -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: IO Exception: Connection reset by peer: socket write error
Agreed on that one. However, back to the issue, this is not letting me log back in to the application. And, it's not throwing an exception in the filter that I have that gets/releases DB connections from a connection pool. When the application is run over in the same network as the DB there is no problem at all. Just when I run it from a different location it seems to act up in this manner. That's why I'm not quite sure. Turner, John [EMAIL PROTECTED] wrote: Never mind...I missed the part about the DB. *sigh* ...time for an after work beer. John -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 4:45 PM To: 'Tomcat Users List' Subject: RE: IO Exception: Connection reset by peer: socket write error Agreed, though in my experience connection reset by peer messages mean the browser/client has stopped accepting data from the server, for various reasons: timeouts, closing the browser window, etc. In most situations, they are harmless. John -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 4:41 PM To: Tomcat Users List Subject: RE: IO Exception: Connection reset by peer: socket write error Howdy, You're going to need to give us a lot more than that ;) What tomcat version, what connectors, full stack trace / log if possible, etc... ;) Yoav Shapira Millennium ChemInformatics -- To unsubscribe, e-mail: For additional commands, e-mail: - Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
JDBC: Socket closed connection reset by peer
Hi. I'm using PostgreSQL (7.2) as backend database for my application and for the JDBCRealm. After some time (typically during night), I get SQLExceptions caused by the socket being either closed or reset by peer. Anybody having (had) similar problems (and solved them)? Versions are Tomcat 4.0.3, JDK 1.4, RedHat 7.3. Yours, Haakon Hansen Norway -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Error: Connection reset by peer: socket write error
Hello, everybody I know that everybody love Error message ... but maybe someone can help me. I have this error on my tomcat window 2002-05-22 11:36:05 - Ctx(/jetspeed) : IOException in R( /jetspeed + /images/btn_persoHTML_allume.gif + null) - java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite(Native Method) (...) Does anybody knows where it comes from, is it an error from tomcat or jetspeed. (I think tomcat but am not sure) However, html page is well displayed with the image /images/btn_persoHTML_allume.gif Any help would be greatly appreciate :) Pierre Besson-Deblon -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Error: Connection reset by peer: socket write error
Hi , we have this error message too, our Tomcat version is 3.2.1 which is running on Window 2000 Server. If we switch to 3.3.1 or 4.0x maybe it is going to be ok ?? any idea ? and one more question how can i add new jar files to Tomcat 3.3.1. I paste all need jar files (for example : jfreechart0.8.4.jar) to lib\comman\ but it doesnt work and then i cut these jar files from there and paste them to lib\container but the result is same . What must i do ? any idea ? Regards Altug. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 22, 2002 1:08 PM Subject: Error: Connection reset by peer: socket write error Hello, everybody I know that everybody love Error message ... but maybe someone can help me. I have this error on my tomcat window 2002-05-22 11:36:05 - Ctx(/jetspeed) : IOException in R( /jetspeed + /images/btn_persoHTML_allume.gif + null) - java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite(Native Method) (...) Does anybody knows where it comes from, is it an error from tomcat or jetspeed. (I think tomcat but am not sure) However, html page is well displayed with the image /images/btn_persoHTML_allume.gif Any help would be greatly appreciate :) Pierre Besson-Deblon -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Error: Connection reset by peer: socket write error
I am using Tomcat 4.0.3 on win32 and get the same error. I do not think that upgrading will help. In my case the error is not causing any problems so I have not worried much about it -Chris -Original Message- From: Altug B. Altintas [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 22, 2002 10:48 AM To: Tomcat Users List Subject: Re: Error: Connection reset by peer: socket write error Hi , we have this error message too, our Tomcat version is 3.2.1 which is running on Window 2000 Server. If we switch to 3.3.1 or 4.0x maybe it is going to be ok ?? any idea ? and one more question how can i add new jar files to Tomcat 3.3.1. I paste all need jar files (for example : jfreechart0.8.4.jar) to lib\comman\ but it doesnt work and then i cut these jar files from there and paste them to lib\container but the result is same . What must i do ? any idea ? Regards Altug. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 22, 2002 1:08 PM Subject: Error: Connection reset by peer: socket write error Hello, everybody I know that everybody love Error message ... but maybe someone can help me. I have this error on my tomcat window 2002-05-22 11:36:05 - Ctx(/jetspeed) : IOException in R( /jetspeed + /images/btn_persoHTML_allume.gif + null) - java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite(Native Method) (...) Does anybody knows where it comes from, is it an error from tomcat or jetspeed. (I think tomcat but am not sure) However, html page is well displayed with the image /images/btn_persoHTML_allume.gif Any help would be greatly appreciate :) Pierre Besson-Deblon -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Error: Connection reset by peer: socket write error
I have W2k server and tomcat 3.3.1, maybe a problem with w2k server, has some else the same kind of error ? or better an idea where the problem comes from ? For your problem of path, I think lib\apps\ is the directory for jar files you may use in your servlets... but I don't use tomcat directly (using jetspeed-turbine) Pierre. Altug B. AltintasPour :Tomcat Users List [EMAIL PROTECTED] altuga@riskturk.cc : com Objet : Re: Error: Connection reset by peer: socket write error 22/05/2002 16:47 Veuillez répondre à Tomcat Users List Hi , we have this error message too, our Tomcat version is 3.2.1 which is running on Window 2000 Server. If we switch to 3.3.1 or 4.0x maybe it is going to be ok ?? any idea ? and one more question how can i add new jar files to Tomcat 3.3.1. I paste all need jar files (for example : jfreechart0.8.4.jar) to lib\comman\ but it doesnt work and then i cut these jar files from there and paste them to lib\container but the result is same . What must i do ? any idea ? Regards Altug. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 22, 2002 1:08 PM Subject: Error: Connection reset by peer: socket write error Hello, everybody I know that everybody love Error message ... but maybe someone can help me. I have this error on my tomcat window 2002-05-22 11:36:05 - Ctx(/jetspeed) : IOException in R( /jetspeed + /images/btn_persoHTML_allume.gif + null) - java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite(Native Method) (...) Does anybody knows where it comes from, is it an error from tomcat or jetspeed. (I think tomcat but am not sure) However, html page is well displayed with the image /images/btn_persoHTML_allume.gif Any help would be greatly appreciate :) Pierre Besson-Deblon -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Error: Connection reset by peer: socket write error
Hi, this error message simply states that the user pressed the STOP-button in her browser, causing the connection to be reset. so you are right when saying: everything's fine - i'll ignore it :) cheers, Peter -Original Message- From: Christopher Moon [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 22, 2002 4:53 PM To: 'Tomcat Users List' Subject: RE: Error: Connection reset by peer: socket write error I am using Tomcat 4.0.3 on win32 and get the same error. I do not think that upgrading will help. In my case the error is not causing any problems so I have not worried much about it -Chris -Original Message- From: Altug B. Altintas [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 22, 2002 10:48 AM To: Tomcat Users List Subject: Re: Error: Connection reset by peer: socket write error Hi , we have this error message too, our Tomcat version is 3.2.1 which is running on Window 2000 Server. If we switch to 3.3.1 or 4.0x maybe it is going to be ok ?? any idea ? and one more question how can i add new jar files to Tomcat 3.3.1. I paste all need jar files (for example : jfreechart0.8.4.jar) to lib\comman\ but it doesnt work and then i cut these jar files from there and paste them to lib\container but the result is same . What must i do ? any idea ? Regards Altug. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 22, 2002 1:08 PM Subject: Error: Connection reset by peer: socket write error Hello, everybody I know that everybody love Error message ... but maybe someone can help me. I have this error on my tomcat window 2002-05-22 11:36:05 - Ctx(/jetspeed) : IOException in R( /jetspeed + /images/btn_persoHTML_allume.gif + null) - java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite(Native Method) (...) Does anybody knows where it comes from, is it an error from tomcat or jetspeed. (I think tomcat but am not sure) However, html page is well displayed with the image /images/btn_persoHTML_allume.gif Any help would be greatly appreciate :) Pierre Besson-Deblon -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Error: Connection reset by peer: socket write error
Unfortunatley, it is not somebody pressing the stop button in the browser. I setup a separate apache instance to test that theory and I would still get the same error when I connected and I am positive that I did not press the stop button. -Chris -Original Message- From: Peter Romianowski [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 22, 2002 11:02 AM To: Tomcat Users List Subject: RE: Error: Connection reset by peer: socket write error Hi, this error message simply states that the user pressed the STOP-button in her browser, causing the connection to be reset. so you are right when saying: everything's fine - i'll ignore it :) cheers, Peter -Original Message- From: Christopher Moon [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 22, 2002 4:53 PM To: 'Tomcat Users List' Subject: RE: Error: Connection reset by peer: socket write error I am using Tomcat 4.0.3 on win32 and get the same error. I do not think that upgrading will help. In my case the error is not causing any problems so I have not worried much about it -Chris -Original Message- From: Altug B. Altintas [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 22, 2002 10:48 AM To: Tomcat Users List Subject: Re: Error: Connection reset by peer: socket write error Hi , we have this error message too, our Tomcat version is 3.2.1 which is running on Window 2000 Server. If we switch to 3.3.1 or 4.0x maybe it is going to be ok ?? any idea ? and one more question how can i add new jar files to Tomcat 3.3.1. I paste all need jar files (for example : jfreechart0.8.4.jar) to lib\comman\ but it doesnt work and then i cut these jar files from there and paste them to lib\container but the result is same . What must i do ? any idea ? Regards Altug. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 22, 2002 1:08 PM Subject: Error: Connection reset by peer: socket write error Hello, everybody I know that everybody love Error message ... but maybe someone can help me. I have this error on my tomcat window 2002-05-22 11:36:05 - Ctx(/jetspeed) : IOException in R( /jetspeed + /images/btn_persoHTML_allume.gif + null) - java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite(Native Method) (...) Does anybody knows where it comes from, is it an error from tomcat or jetspeed. (I think tomcat but am not sure) However, html page is well displayed with the image /images/btn_persoHTML_allume.gif Any help would be greatly appreciate :) Pierre Besson-Deblon -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
AW: Error: Connection reset by peer: socket write error
Have a look at http://www.aswethink.com/employees/randy/tomcat/IOException.html -Ursprüngliche Nachricht- Von: Christopher Moon [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 22. Mai 2002 17:10 An: 'Tomcat Users List' Betreff: RE: Error: Connection reset by peer: socket write error Unfortunatley, it is not somebody pressing the stop button in the browser. I setup a separate apache instance to test that theory and I would still get the same error when I connected and I am positive that I did not press the stop button. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
connection reset by peer: socket write error
Hi all, Would anyone please tell me what causes the exceptions java.net.SocketException: Connection reset by peer and Connection aborted by peer socket write error? How do I avoid such problem? Thanks in advance for you help. David -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Connection reset..
It usually happens when user closes connection (e.g. Stop button in browser) but I think it possibly can be bug as well. So, I tryed to raise the question if servlet programmer should be able to detect client connection closing. But without success :(( As far as I know, RFC 2616 tells that server SHOULD monitor the connection to prevent loss of resources. - Original Message - From: Ravindra K. Bhat [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, January 16, 2002 6:11 PM Subject: Connection reset.. What does... IOException in: connection rest by peer: socket write error..mean? and how can you fix it? Anton -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Connection reset..
What does... IOException in: connection rest by peer: socket write error..mean? and how can you fix it? -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Loading images - connection reset by peer: socket write error
Hi. Tomcat keeps issuing this message every time a servlet references an image: Ctx ( /Gedol ): IOException in R( /Gedol + /images/cubo.gif + null ) Connection reset by peer: socket write error, where 'Gedol' is my app with a subfolder named 'images' where I put all the images. The servlets generate the pages properly, though. What does this mean and what should I do about it? Any help will be much appreciated. Thanks in advance. Pedro. *** Pedro Gaspar PT Prime DMK / GSV Tel: +351 21 500 41 43 Fax: +351 21 500 45 85 Email: [EMAIL PROTECTED] *** -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Loading images - connection reset by peer: socket write error
You should do nothing. The error is from the clients browser closing the connection. It's normal. /Christopher -Original Message- From: Pedro F Gaspar [mailto:[EMAIL PROTECTED]] Sent: den 11 december 2001 10:36 To: [EMAIL PROTECTED] Subject: Loading images - connection reset by peer: socket write error Hi. Tomcat keeps issuing this message every time a servlet references an image: Ctx ( /Gedol ): IOException in R( /Gedol + /images/cubo.gif + null ) Connection reset by peer: socket write error, where 'Gedol' is my app with a subfolder named 'images' where I put all the images. The servlets generate the pages properly, though. What does this mean and what should I do about it? Any help will be much appreciated. Thanks in advance. Pedro. *** Pedro Gaspar PT Prime DMK / GSV Tel: +351 21 500 41 43 Fax: +351 21 500 45 85 Email: [EMAIL PROTECTED] *** -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Loading images - connection reset by peer: socket write error
Hi, Now, if the servlet *generates* the image (ie it returns a content-type image/jpeg for example), and if the IOException shows up before the buffer is closed, Tomcat dies, which is annoying. How could we prevent that ? Regards, Guillaume Mathe Smartinnov Original message from: Cato, Christopher You should do nothing. The error is from the clients browser closing the connection. It's normal. /Christopher -Original Message- From: Pedro F Gaspar [mailto:[EMAIL PROTECTED]] Sent: den 11 december 2001 10:36 To: [EMAIL PROTECTED] Subject: Loading images - connection reset by peer: socket write error Hi. Tomcat keeps issuing this message every time a servlet references an image: Ctx ( /Gedol ): IOException in R( /Gedol + /images/cubo.gif + null ) Connection reset by peer: socket write error, where 'Gedol' is my app with a subfolder named 'images' where I put all the images. The servlets generate the pages properly, though. What does this mean and what should I do about it? Any help will be much appreciated. Thanks in advance. Pedro. *** Pedro Gaspar PT Prime DMK / GSV Tel: +351 21 500 41 43 Fax: +351 21 500 45 85 Email: [EMAIL PROTECTED] *** -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Connection reset by peer
May I recommand you to switch to Tomcat 3.3, for strict 2.2/1.1 RI, which fixes quantities of problems like this ? The RI for 2.2/1.1 is Tomcat 3.3 today, just take a look at java.sun.com :) - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: Muhammad Ali Siddiqui [mailto:[EMAIL PROTECTED]] Sent: Monday, December 10, 2001 9:02 PM To: Tomcat Developers List; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Connection reset by peer Hello, I had the same problem with tomcat in windows environment. Its just that when ever your connection between Tomcat and its client (mostly a web browser) breaks (may be due to pressing stop button in the browser or due to any other reason) it throws exception. And the exception stack trace was printed on the console. So nothing to worry about this. I am not too sure, but I guess your tomcat didn't hang due to this reason. There must be some other problem with your environment as well. Regards, Ali. - Original Message - From: Renato [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, December 10, 2001 5:26 PM Subject: Connection reset by peer Hi all, I was looking through tomcat's log ( tomcat 3.2.4 + mod_jk under Red Hat 7.2 + Sun JVM 1.3.1_01 ) and I saw a lot of messages like this: java.net.SocketException: Connection reset by peer: Connection reset by peer at java.net.SocketInputStream.socketRead(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:86) at org.apache.tomcat.service.connector.TcpConnector.receiveFully (TcpConnector.java:150) at org.apache.tomcat.service.connector.TcpConnector.receive (TcpConnector.java:121) at org.apache.tomcat.service.connector.Ajp13ConnectionHandler.proc essConnection (Ajp13ConnectionHandler.ja va:146) at org.apache.tomcat.service.TcpWorkerThread.runIt (PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run (ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484) After a while Tomcat starts failing to respond till it hangs completely. I've seen Sun's JVM release and already set up the 'work around' parameters for Linux. Any other hint ? Thanks Renato. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Connection reset by peer
Hi all, I was looking through tomcat's log ( tomcat 3.2.4 + mod_jk under Red Hat 7.2 + Sun JVM 1.3.1_01 ) and I saw a lot of messages like this: java.net.SocketException: Connection reset by peer: Connection reset by peer at java.net.SocketInputStream.socketRead(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:86) at org.apache.tomcat.service.connector.TcpConnector.receiveFully (TcpConnector.java:150) at org.apache.tomcat.service.connector.TcpConnector.receive (TcpConnector.java:121) at org.apache.tomcat.service.connector.Ajp13ConnectionHandler.processConnection (Ajp13ConnectionHandler.ja va:146) at org.apache.tomcat.service.TcpWorkerThread.runIt (PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run (ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484) After a while Tomcat starts failing to respond till it hangs completely. I've seen Sun's JVM release and already set up the 'work around' parameters for Linux. Any other hint ? Thanks Renato. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Connection reset by peer
It looks that this error however is happening at the connector pool level. I see other 'connection reset by peer' errors but they have different stacks. This one looks more critical. It might also a bug in the JVM. Hello, I had the same problem with tomcat in windows environment. Its just that when ever your connection between Tomcat and its client (mostly a web browser) breaks (may be due to pressing stop button in the browser or due to any other reason) it throws exception. And the exception stack trace was printed on the console. So nothing to worry about this. I am not too sure, but I guess your tomcat didn't hang due to this reason. There must be some other problem with your environment as well. Regards, Ali. - Original Message - From: Renato [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, December 10, 2001 5:26 PM Subject: Connection reset by peer Hi all, I was looking through tomcat's log ( tomcat 3.2.4 + mod_jk under Red Hat 7.2 + Sun JVM 1.3.1_01 ) and I saw a lot of messages like this: java.net.SocketException: Connection reset by peer: Connection reset by peer at java.net.SocketInputStream.socketRead(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:86) at org.apache.tomcat.service.connector.TcpConnector.receiveFully (TcpConnector.java:150) at org.apache.tomcat.service.connector.TcpConnector.receive (TcpConnector.java:121) at org.apache.tomcat.service.connector.Ajp13ConnectionHandler.processConnection (Ajp13ConnectionHandler.ja va:146) at org.apache.tomcat.service.TcpWorkerThread.runIt (PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run (ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484) After a while Tomcat starts failing to respond till it hangs completely. I've seen Sun's JVM release and already set up the 'work around' parameters for Linux. Any other hint ? Thanks Renato. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Connection reset by peer
hello i am encountering this problem,and believe me,i have xhausted this forum..and lloked for all possible solutions.Finally i am posting this to find some help i have deployed a JSP(BC4J JSP application developed in JDeveloper 3.2.3) application to Tomcat 3.2.3. the application runs fine sometimes,but sometimes,when i try to refresh a jsp page,the jsp page outputs only part of the page.The full page is not seen,if i see the source of th page,i see Error:null and in Tomcat Console i see IOException,Connection reset by peer if i keep refreshing the page,it loads the complete page at some point.Otherwise i have to restart my appliation and keep struggling again. Any help for this? Regards Monali -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Connection reset by peer
Nakhate, Monali wrote: hello i am encountering this problem,and believe me,i have xhausted this forum..and lloked for all possible solutions.Finally i am posting this to find some help i have deployed a JSP(BC4J JSP application developed in JDeveloper 3.2.3) application to Tomcat 3.2.3. the application runs fine sometimes,but sometimes,when i try to refresh a jsp page,the jsp page outputs only part of the page.The full page is not seen,if i see the source of th page,i see Error:null and in Tomcat Console i see IOException,Connection reset by peer if i keep refreshing the page,it loads the complete page at some point.Otherwise i have to restart my appliation and keep struggling again. Any help for this? Regards Monali How long is it taking the JSP page to generate and display? Usually the Connection Reset by Peer is because the luser on the other side of the browser has pressed the stop button in the middle of a request. It started to show up alot more with HTTP/1.1 and request pipelining. If it's taking a long time for the JSP to generate could the browser be timing out and shutting down the connection? Are you using MSIE? It has some really bad Keep Alive logic in it (at least with the 5.x strain, I haven't tested out the 6.x strain fully yet). And get the DirecTV US people to send TheWB and UPN to us folks in Atlanta. Buffy and Angel and Smallville over Rabbit Ears sucks. -- Steve Brunton [EMAIL PROTECTED] Phone: 404-827-2756 Chief Engineer Enterprise SystemsOne CNN Center, Atlanta GA CNN Internet Technologies ICBM: 84W 23' 45 33N 45' 29 * Reality is an illusion that occurs due to lack of alcohol. * -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Connection reset by peer
hello i am encountering this problem,and believe me,i have xhausted this forum..and lloked for all possible solutions.Finally i am posting this to find some help i have deployed a JSP(BC4J JSP application developed in JDeveloper 3.2.3) application to Tomcat 3.2.3. the application runs fine sometimes,but sometimes,when i try to refresh a jsp page,the jsp page outputs only part of the page.The full page is not seen,if i see the source of th page,i see Error:null and in Tomcat Console i see IOException,Connection reset by peer if i keep refreshing the page,it loads the complete page at some point.Otherwise i have to restart my appliation and keep struggling again. Any help for this? Regards Monali Monali Nakhate Software Systems Group DIRECTV* Latin America, LLC 2400 E. Commercial Boulevard 9th Fl. Fort Lauderdale, FLORIDA 33308-4030 Tel: (954)-958-3260 Fax: (954)-958-3433 -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Connection reset by peer: socket write error NOT harmless
Hello List!
This is my first post here, so sorry for the length.
I'm running a binary distribution of tomcat 3.2.3 on Windows NT, developing
in JDDeveloper 3.2.2.
I have a client java program which sends a simple SQL string to a servlet
which gets an image from our database and returns it. No browsers involved.
The problem I'm having is that a third of the time when I execute the client
request from my computer to the local IP address of tomcat, also running on
my computer, tomcat gives this error message:
2001-08-13 15:39:03 - Ctx( /databasefetcher ): IOException in:
( /databasefetcher + /servlet/databasefetcher + null) Connection reset by
peer: socket write error
And the file, which the client program writes to the file system, is
corrupted.
If tomcat does not give this error message, the image is fine and can be
opened and enjoyed for all of its beauty.
The images are tiffs and are about 250K in size each. Below is the code for
the fetching:
+
public void doPost(HttpServletRequest req, HttpServletResponse res)
throws ServletException,
IOException{
//read in the SQL string
BufferedReader br = new BufferedReader(new
InputStreamReader(req.getInputStream()));
String SQL = +br.readLine();
try{
//get the image from the database
ResultSet rs = (ResultSet)Enterpriser.dealWithDbFetch(SQL, false);
InputStream isImg=null;
if(rs.next()){
isImg = rs.getBinaryStream(1);
}
//set the length to 1.3 mb, the largest image size
res.setContentLength(130);
res.setContentType(image/tif);
res.setBufferSize(130);
byte[] b = new byte[130];
//read the image into the inputstream
isImg.read( b );
//get the servlet output stream
ServletOutputStream out = res.getOutputStream();
//write the image to the response
out.write(b);
out.close();
}
catch(Exception e){
e.printStackTrace();
}
}
AND here is the code for the client program:
++
import java.net.*;
import java.io.*;
import org.xml.sax.*;
import java.util.Properties;
public class StringHttp {
// POST an XML document to a Service's URL, Returning XML document
response
public static InputStream doPost(String stringToPost, URL target)
throws IOException, ProtocolException {
// (1) Open an HTTP connection to the target URL
HttpURLConnection conn = (HttpURLConnection)target.openConnection();
if (conn == null) return null;
// (2) Use HTTP POST
conn.setRequestMethod(POST);
// (3) Indicate that the content type is plain text with appropriate
MIME type
conn.setRequestProperty(Content-type,text/plain);
// (4) We'll be writing and reading from the connection
conn.setDoOutput(true);
conn.setDoInput(true);
// (5) Print the String into the connection's output stream
PrintWriter pw = new PrintWriter( new
utputStreamWriter( conn.getOutputStream()));
pw.println( stringToPost );// etc, etc.
pw.flush();
pw.close();
// (6) Get an InputStream to read the response from the server.
InputStream responseStream = conn.getInputStream();
return responseStream;
}
public static void main(String args[]){
String SQL=Select A.MAP from a TABLE where map_id=1;
try{
URL dispatchURL = new
URL(http://192.1.1.215:8080/databasefetcher/servlet/databasefetcher;);
long start = System.currentTimeMillis();
InputStream is = StringHttp.doPost(SQL, dispatchURL);
long end = System.currentTimeMillis()-start;
System.out.println(Took + end+ millis);
byte[] b = new byte[130];
is.read(b);
FileOutputStream fos = new FileOutputStream(new
File(C:\\imgTest3.tif));
fos.write(b);
}
catch(Exception e){
e.printStackTrace();
}
}
}
+
I've seen a number of posts on this subject and the answer always seems to
have to do with IE. I'm not using it. Though sometimes IIS starts up
acidentally, cutting apache out of the loop.
Any help is greatly appreciated.
Thanks,
Alex
RE: Connection reset by peer: socket write error NOT harmless
Just to give you some more background info(you being the kind hearted soul
who read my last post) The image is ALWAYS corrupted if I run the client
program from another machine on our local network.
Also, if I add the following line of code to the servlet:
out.flush();
sandwiched between:
out.write(b);
out.close();
I get a much more robust error, namely:
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
Thanks again .
Alex
-Original Message-
From: alex reuter [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 13, 2001 4:10 PM
To: [EMAIL PROTECTED]
Subject: Connection reset by peer: socket write error NOT harmless
Hello List!
This is my first post here, so sorry for the length.
I'm running a binary distribution of tomcat 3.2.3 on Windows NT, developing
in JDDeveloper 3.2.2.
I have a client java program which sends a simple SQL string to a servlet
which gets an image from our database and returns it. No browsers involved.
The problem I'm having is that a third of the time when I execute the client
request from my computer to the local IP address of tomcat, also running on
my computer, tomcat gives this error message:
2001-08-13 15:39:03 - Ctx( /databasefetcher ): IOException in:
( /databasefetcher + /servlet/databasefetcher + null) Connection reset by
peer: socket write error
And the file, which the client program writes to the file system, is
corrupted.
If tomcat does not give this error message, the image is fine and can be
opened and enjoyed for all of its beauty.
The images are tiffs and are about 250K in size each. Below is the code for
the fetching:
+
public void doPost(HttpServletRequest req, HttpServletResponse res)
throws ServletException,
IOException{
//read in the SQL string
BufferedReader br = new BufferedReader(new
InputStreamReader(req.getInputStream()));
String SQL = +br.readLine();
try{
//get the image from the database
ResultSet rs = (ResultSet)Enterpriser.dealWithDbFetch(SQL, false);
InputStream isImg=null;
if(rs.next()){
isImg = rs.getBinaryStream(1);
}
//set the length to 1.3 mb, the largest image size
res.setContentLength(130);
res.setContentType(image/tif);
res.setBufferSize(130);
byte[] b = new byte[130];
//read the image into the inputstream
isImg.read( b );
//get the servlet output stream
ServletOutputStream out = res.getOutputStream();
//write the image to the response
out.write(b);
out.close();
}
catch(Exception e){
e.printStackTrace();
}
}
AND here is the code for the client program:
++
import java.net.*;
import java.io.*;
import org.xml.sax.*;
import java.util.Properties;
public class StringHttp {
// POST an XML document to a Service's URL, Returning XML document
response
public static InputStream doPost(String stringToPost, URL target)
throws IOException, ProtocolException {
// (1) Open an HTTP connection to the target URL
HttpURLConnection conn = (HttpURLConnection)target.openConnection();
if (conn == null) return null;
// (2) Use HTTP POST
conn.setRequestMethod(POST);
// (3) Indicate that the content type is plain text with appropriate
MIME type
conn.setRequestProperty(Content-type,text/plain);
// (4) We'll be writing and reading from the connection
conn.setDoOutput(true);
conn.setDoInput(true);
// (5) Print the String into the connection's output stream
PrintWriter pw = new PrintWriter( new
utputStreamWriter( conn.getOutputStream()));
pw.println( stringToPost );// etc, etc.
pw.flush();
pw.close();
// (6) Get an InputStream to read the response from the server.
InputStream responseStream = conn.getInputStream();
return responseStream;
}
public static void main(String args[]){
String SQL=Select A.MAP from a TABLE where map_id=1;
try{
URL dispatchURL = new
URL(http://192.1.1.215:8080/databasefetcher/servlet/databasefetcher;);
long start = System.currentTimeMillis();
InputStream is = StringHttp.doPost(SQL, dispatchURL);
long end = System.currentTimeMillis()-start;
System.out.println(Took + end+ millis);
byte[] b = new byte[130];
is.read(b);
FileOutputStream fos = new FileOutputStream(new
File(C:\\imgTest3.tif));
fos.write(b);
}
catch(Exception e){
e.printStackTrace();
}
}
}
+
I've seen a number of posts on this subject and the answer always seems to
have to do with IE. I'm not using it. Though sometimes IIS starts up
acidentally, cutting apache out
java.net.SocketException: Connection reset by peer
Hi, Pelease help.. I'm getting the following error so far using Tomcat 3.2.2 on Solaris 8, but I get the following error popping out on the tomcat console randomly after page output is successfully fed to a client, sometimes it appears, sometimes it doesn't. The main problem is server got down after running tomcat overnight. Some times it will automatically removing all the contexts and got down the server. do you have any idea about this problem , what would be the cause of this. The error is 2001-08-10 04:10:39 - ContextManager: SocketException reading request, ignored - java.net.SocketException: Connection reset by peer at java.net.PlainSocketImpl.socketAvailable(Native Method) at java.net.PlainSocketImpl.available(PlainSocketImpl.java:436) at java.net.SocketInputStream.available(SocketInputStream.java:141) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnectio n(HttpConnectionHandler.java:217) at org.apache.tomcat.service.TcpWorkerThread.runIt(Compiled Code) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(Compiled Code) at java.lang.Thread.run(Compiled Code) Best Regards, Raju Jacob
RE: java.net.SocketException: Connection reset by peer
This can be normal. I have seen IIS, after determining that a resource it has cached hasn't been updated, simply close the connection rather that continue reading the response. This would result an error like what you are seeing. Larry -Original Message- From: Raju Jacob [mailto:[EMAIL PROTECTED]] Sent: Friday, August 10, 2001 4:46 AM To: [EMAIL PROTECTED] Subject: java.net.SocketException: Connection reset by peer Hi, Pelease help.. I'm getting the following error so far using Tomcat 3.2.2 on Solaris 8, but I get the following error popping out on the tomcat console randomly after page output is successfully fed to a client, sometimes it appears, sometimes it doesn't. The main problem is server got down after running tomcat overnight. Some times it will automatically removing all the contexts and got down the server. do you have any idea about this problem , what would be the cause of this. The error is -- -- 2001-08-10 04:10:39 - ContextManager: SocketException reading request, ignored - java.net.SocketException: Connection reset by peer at java.net.PlainSocketImpl.socketAvailable(Native Method) at java.net.PlainSocketImpl.available(PlainSocketImpl.java:436) at java.net.SocketInputStream.available(SocketInputStream.java:141) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnectio n(HttpConnectionHandler.java:217) at org.apache.tomcat.service.TcpWorkerThread.runIt(Compiled Code) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(Compiled Code) at java.lang.Thread.run(Compiled Code) -- -- Best Regards, Raju Jacob
socket write and Connection reset by peer
Hi I am getting frequently these errors. I am using some flash and gif files in my jsp page. For each and every image i am using i am getting the following errors. But the pages displaying properly. Ctx( ): IOException in: R( + /ssp/jsp/righttop.swf + null) socket write error (code=10053) Ctx( ): IOException in: R( + /ssp/jsp/true.gif + null) Connection reset by peer: socket write error Can any one know about this errors. Tell me how to remove these errors from the console. regards venkatesh
Re: socket write and Connection reset by peer
Network programmers! I also frequently get code=10053 error although not w/Tomcat. I learned to work around it, but would be nice to know the origins of this code. thanks, luba - Original Message - From: Venkatesh T [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, June 18, 2001 6:40 AM Subject: socket write and Connection reset by peer Hi I am getting frequently these errors. I am using some flash and gif files in my jsp page. For each and every image i am using i am getting the following errors. But the pages displaying properly. Ctx( ): IOException in: R( + /ssp/jsp/righttop.swf + null) socket write error (code=10053) Ctx( ): IOException in: R( + /ssp/jsp/true.gif + null) Connection reset by peer: socket write error Can any one know about this errors. Tell me how to remove these errors from the console. regards venkatesh
Connection Reset by Peer with Tomcat 3.1 on RH Linux 6.1
Hello, I have been using Tomcat 3.1 for 4 months under Windows 2000 with and without IIS "integration". It seems to work fine. I just started using it under Red Hat Linux 6.1 (Lunux kernel 2.2.12-20) and the JVM is "JVM.1.3.0beta_refresh-b09". After the tomcat has been running and apparently working just fine, I will (out of nowhere) receive Connection Reset by Peer messages to the console. I get this just running the "examples" web site provided with tomcat. Any ideas? Is there a newer JVM around that will help? Could you email me if you have any info? At [EMAIL PROTECTED] Thanks. Mike Papper
Connection reset by peer on image rollover
Hi A new problem appeared recently on my Tomcat 3.2B6 + Struts 0.5 application. I am experiencing more and more "Connection reset by peer" exceptions. Could it be: - A bug in my code, though I don't remind big changes and it seems to appear in all the pages, even those untouched... - A new feature in the new SP1 for Internet Explorer 5.5 and incompatibility with tomcat. - A normal behaviour... I've traced the problem where I can sometimes reproduce it to some image rollover buttons. From my understanding, if the the mouse fires a image change in the rollover, the browser should change the image without the need for a new connection to the server as all the images have been loaded in its cache. I've tried to reproduce the problem with Nestcape 6 Beta 2 but it doesn't fire on the rollover buttons. And the final version of Netscape 6 doesn't want to setup on my PC! Here is the exception stack: 2000-11-16 11:59:28 - PoolTcpEndpoint: Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080] ignored exception: java.net.SocketException: Connection reset by peer - java.net.SocketException: Connection reset by peer at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413) at java.net.ServerSocket.implAccept(ServerSocket.java:243) at java.net.ServerSocket.accept(ServerSocket.java:222) at org.apache.tomcat.service.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java: 286) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:393) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498) at java.lang.Thread.run(Thread.java:484) I can't explain the addresses and port parameter for ServerSocket. Could someone share some light with me? Pierre Métras
Is there an archive of this list that can be searched and question on Error reading request: connection reset
As the subject says, is there an archive of this list that can be searched. I don't like asking questions that have already been answered before, so I would like to first look at what has been said in the past. Anyways, I do have a question. I'm running Tomcat 3.1 standalone and I'm getting the following error in the error log "Error reading request: connection reset". This occurs even when just serving static html resources. Any ideas on what this means and what might be causing it.
Re: Is there an archive of this list that can be searched and question on Error reading request: connection reset
There are possibly three archives. Check: http://marc.theaimsgroup.com/?l=tomcat-userr=1w=2 Julio - Original Message - From: Brett Bergquist [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, November 16, 2000 8:39 PM Subject: Is there an archive of this list that can be searched and question on "Error reading request: connection reset" As the subject says, is there an archive of this list that can be searched. I don't like asking questions that have already been answered before, so I would like to first look at what has been said in the past. Anyways, I do have a question. I'm running Tomcat 3.1 standalone and I'm getting the following error in the error log "Error reading request: connection reset". This occurs even when just serving static html resources. Any ideas on what this means and what might be causing it.
