Are you using the servlet to connect to another socket?
If so, you should try synchronizing access to the socket and not closing the
connection prematurely.
Or use a single-threaded model for your servlet so only 1 request at a time
will be served and avoid socket connection being reset.
I believe the "connection reset by peer" error results when socket A
connects to socket B and socket B suddenly closes the connection when socket
A is still receiving data. Hope this helps.
:^)
Ricky Y. Artigas
Analyst/Programmer
Information Technology Division
Easycall Communications Phils., Inc.
- Easycall Internet -
418 Arayat St., Mandaluyong City 1550, Philippines
Personal WAP Site: http://www.buzzed.co.uk/mobile/?rya
Company Website: http://www.easycall.com.ph
Tel.no: (+632) 5338001 ext.6574
Mobile:(+63) 0917-8951783
Pager: 141-002955
Email: [EMAIL PROTECTED]
> -------------------------------
> IMPORTANT NOTICE:
> This message (and any attachment hereto) may contain privileged and/or
> confidential information specific to EasyCall. If you are not the intended
> addressee indicated in this message, you may not copy or disseminate this
> message (or any attachment hereto) to anyone. Instead, please destroy this
> message (and any attachment hereto), and kindly notify the sender by reply
> email. Any information in this message (and any attachment thereto) that
> do not relate to the official business of EasyCall shall be understood as
> neither given nor endorsed by the company.
>
>
> -----Original Message-----
> From: Jaimes Blunt [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, May 18, 2001 1:22 AM
> To: Jakarta-Tomcat-User (E-mail)
> Subject: Tomcat Socket Error
>
> Hi guys,
>
> I was wondering if someone could help me.� I am using Tomcat as a
> standalone middleware server, that basically manages connections to a
> remote system, and parses all data received.� I have started getting weird
> error messages as mroe people begin to access my servlets.� You can find
> the error message below.� I was wondering if anyone else was encountering
> these kinds of errors, and if so, what they may have done to solve it.
>
> Thanks a bunch
>
> Jaimes Blunt
>
> Here is the error:
> 2001-05-17 10:39:44 - ContextManager: SocketException reading request,
> ignored -
> �java.net.SocketException: Connection reset by peer: JVM_recv in socket
> input st
> ream read
> ������� at java.net.SocketInputStream.socketRead(Native Method)
> ������� at java.net.SocketInputStream.read(SocketInputStream.java:86)
> ������� at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
> ������� at java.io.BufferedInputStream.read(BufferedInputStream.java:204)
> ������� at
> org.apache.tomcat.service.http.HttpRequestAdapter.doRead(HttpRequestAdapte
> r.java:115)
> ������� at
> org.apache.tomcat.core.BufferedServletInputStream.doRead(BufferedServletIn
> putStream.java:106)
> ������� at
> org.apache.tomcat.core.BufferedServletInputStream.read(BufferedServletInpu
> tStream.java:128)
> ������� at
> javax.servlet.ServletInputStream.readLine(ServletInputStream.java:138
> )
> ������� at
> org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequest(HttpRequ
> estAdapter.java:129)
> ������� at
> org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(Htt
> pConnectionHandler.java:195)
> ������� at
> org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
> ������� at
> org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
>
> ������� at java.lang.Thread.run(Thread.java:484)
>
