Bug 37750 - SocketException: Connection reset causes severe error
SocketException: Connection reset causes severe error
Status: RESOLVED WORKSFORME
Product: Tomcat 5
Classification: Unclassified
Component: Connector:HTTP
5.5.12
PC Linux
: P2 minor (vote)
: ---
Assigned To: Tomcat Developers Mailing List
: ErrorMessage
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2005-12-02 06:39 UTC by Arnaud Kleinveld
Modified: 2006-03-28 20:23 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arnaud Kleinveld 2005-12-02 06:39:15 UTC
Lately (looks like after upgrading from 5.5.9) following SocketException errors
appear in catelina.out

SEVERE: Socket error caused by remote host /206.27.238.247
java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(Unknown Source)
        at com.sun.net.ssl.internal.ssl.InputRecord.readFully(Unknown Source)
        at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
        at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
        at
org.apache.tomcat.util.net.jsse.JSSESocketFactory.handshake(JSSESocketFactory.java:119)
        at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:520)
        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(Unknown Source)

It looks like somebody on the internet is accessing our https connection
directly without being redirected from a http connection.

Should a connection reset cause a severe exception?
Comment 1 Yoav Shapira 2005-12-02 16:52:15 UTC
It's not us who chose to categorize this exception as SEVERE ;)  So this never
happened with 5.5.9, only 5.5.12?  
Comment 2 Arnaud Kleinveld 2005-12-04 03:33:13 UTC
I never saw this message when we where running 5.5.9 but I want to be cautious
with saying that it's related to this upgrade. I'm thinking it might also be a
new exploit tried by script kiddies because the clients are accessing the https
connection directly while our appilcation is not designed to do so. Clients are
supposed to be redirected from a http connection and I see no trace of a
previous http request from the same client.
Beside this I'm wondering why this exception is passed on as severe.
Comment 3 nir levy 2006-03-27 09:22:14 UTC
(In reply to comment #1)
> It's not us who chose to categorize this exception as SEVERE ;)  So this never
> happened with 5.5.9, only 5.5.12?  

i got this with 5.5.12 as well, and never with 5.5.9 (but then again 5.5.9 is 
on windows and 5.5.12 is on RHE)
Comment 4 Arnaud Kleinveld 2006-03-29 04:23:15 UTC
I haven't seen this error for months now. I guess it's not related to the
default functionality of tomcat nor our application. From my side of view this
bug may be closed.