[4.0dev] Catalina dies with Connection reset by peer exception

[Stuart Roebuck <sr...@adolos.com>]

I've been using 4.0dev with Cocoon and have an intriguing problem:

Connecting through one web browser I have no problems at all [OmniWeb].   
Connecting through another [IE] Tomcat dies regularly with an uncaught  
java.net.SocketException: Connection reset by peer.  If I repeatedly  
restart Tomcat (whenever it dies) the page I'm accessing eventually appears  
in its entirety, but Tomcat appears to serve only one or two graphics per  
session before death.

Here's the stack trace:

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:90)
   at java.io.BufferedInputStream.fill(BufferedInputStream.java:190)
   at java.io.BufferedInputStream.read(BufferedInputStream.java:208)
   at  
org.apache.catalina.connector.http.HttpProcessor.read(HttpProcessor.java:865)
   at  
org.apache.catalina.connector.http.HttpProcessor.parseRequest(HttpProcessor.java:608)
   at  
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:756)
   at  
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:904)
   at java.lang.Thread.run(Thread.java:479)

With my limited knowledge I would have thought that a 'connection reset by  
peer' exception should just be caught with the specific operation being  
abandoned, but Tomcat staying up.

Is this a known bug in Tomcat/Catalina,  a configuration fault at my end,   
or perhaps a JVM specific issue?


Thanks,

Stuart.

Re: Minor things in Tomcat-4.0 build.xml

[Pierre Delisle <pi...@sun.com>]

Bob,

Thanks for your feedback on the build procedure of tomcat-4.0.
Comments included below.
Please get the latest sources for the fixes. 

> I have been checking out and building tomcat-4.0 lately, and I
> just thought I would point out a few minor typos in the
> build.xml files.
> 
> 1.  In <toplevel>/build.xml and catalina/build.xml, regexp.jar's location is:
> 
>   <property name="regexp.jar"      value="${regexp.home}/bin/jakarta-regexp-1.1.jar"/>
>
> Apparently is has moved in the nightly .zip and it now appears to be:
> 
>   <property name="regexp.jar"      value="${regexp.home}/jakarta-regexp-1.1.jar"/>

Given that the jar file may reside in a different location depending whether 
one uses the source or binary distribution, REGEXP_HOME must now be specified
and the script expects to find the jar file at the top level.
(when using the source distribution, then REGEXP_HOME must point to the
bin directory of the install)

> 
> 2.  Also, the name "jaxp.jar" no longer exists in build.xml, so I changed the javac
> command in catalina/build.xml from
> 
> <javac   srcdir="src/share" destdir="${catalina.build}/classes"
> 
> classpath="${jaxp.jar}:${regexp.jar}:${servlet.jar}:${jcert.jar}:${jnet.jar}:${jsse.jar}"
> 
>          deprecation="off" debug="on" optimize="off" target="1.2"
>          excludes="**/CVS/**"/>
> 
> to
> 
> <javac   srcdir="src/share" destdir="${catalina.build}/classes"
> 
> classpath="${xerces.jar}:${regexp.jar}:${servlet.jar}:${jcert.jar}:${jnet.jar}:${jsse.jar}"
> 
>          deprecation="off" debug="on" optimize="off" target="1.2"
>          excludes="**/CVS/**"/>

Fixed. 

> 3.  However, since Ant needs xerces.jar to run in the first place, then this might
> be redundant, since xerces.jar will need to be in the CLASSPATH.  If so, then possibly
> the build.sh files should have the CP variable as:
> 
> CP=$ANT_HOME/lib/ant.jar:$JAVA_HOME/lib/tools.jar:$XERCES_HOME/xerces.jar

Fixed.

	-- Pierre

Minor things in Tomcat-4.0 build.xml

[Bob Jamison <rj...@lincom-asg.com>]

Hi all,

I have been checking out and building tomcat-4.0 lately, and I
just thought I would point out a few minor typos in the
build.xml files.

1.  In <toplevel>/build.xml and catalina/build.xml, regexp.jar's location is:

  <property name="regexp.jar"      value="${regexp.home}/bin/jakarta-regexp-1.1.jar"/>

Apparently is has moved in the nightly .zip and it now appears to be:

  <property name="regexp.jar"      value="${regexp.home}/jakarta-regexp-1.1.jar"/>

2.  Also, the name "jaxp.jar" no longer exists in build.xml, so I changed the javac
command in catalina/build.xml from

<javac   srcdir="src/share" destdir="${catalina.build}/classes"

classpath="${jaxp.jar}:${regexp.jar}:${servlet.jar}:${jcert.jar}:${jnet.jar}:${jsse.jar}"

         deprecation="off" debug="on" optimize="off" target="1.2"
         excludes="**/CVS/**"/>

to

<javac   srcdir="src/share" destdir="${catalina.build}/classes"

classpath="${xerces.jar}:${regexp.jar}:${servlet.jar}:${jcert.jar}:${jnet.jar}:${jsse.jar}"

         deprecation="off" debug="on" optimize="off" target="1.2"
         excludes="**/CVS/**"/>


3.  However, since Ant needs xerces.jar to run in the first place, then this might
be redundant, since xerces.jar will need to be in the CLASSPATH.  If so, then possibly
the build.sh files should have the CP variable as:

CP=$ANT_HOME/lib/ant.jar:$JAVA_HOME/lib/tools.jar:$XERCES_HOME/xerces.jar



These three items are sufficient for me to do builds on Irix 6.5.2, which I
would consider to be almost a worst-case scenario, as far as portability goes.
I'm not saying I don't love SGI's, but their Java support is lagging somewhat.




Bob Jamison
LinCom Corp