I have the following basic configuration RHEL 5 with Tomcat 5.5.23. This server 
is in a DMZ in my office and from here I can connect to it via LAN rather than 
"the internet".

When I try to download a file (a simple PDF about 1 MB in size) chucked into 
WebContent from the server over the internet it 95% of the time fails due to a 
connection reset event. This happens whether the client I attempt this with is 
a browser or wget. Wget will usually download the file after three or four 
attempts but on one occasion gave up after 20 attempts.

Meanwhile it *never* fails when I download via the LAN.

>From this I thought I had a network issue of some sort but after further 
>testing I have concluded that the problem is either Tomcat or Java on this 
>system.

Not to get overly tedious but I have tried different files (no difference). I 
have looked at where the reset happens (no difference). I looked at and tried 
slightly different config settings (as expected no difference) However when I 
dropped the same file into Apache httpd server on the same server it does work, 
100% on both via LAN and internet.

So at this point if httpd works but tomcat doesn't then I have to think that 
either tomcat or the vm are the cause of the problem. I have searched the bug 
database and google to no real effect, unfortunately connection resets are too 
common a term I think and I am now a bit stuck.

If more information is required I can provide it but are there are any known 
issues that can cause resets to be sent from Tomcat (I assume from prematurely 
closed sockets)?

In the hope that it helps, below is some xx-ed output from running wget on a 
remote box. This is from one of my tests with a larger (15MB) but the idea is 
the same.

wget  http://xxx/example.pdf
--13:24:06--  http://xxx/example.pdf
           => `example.pdf.29'
Resolving xxx... xxx
Connecting to xxx | xxx |:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 15,807,270 (15M) [application/pdf]

 0% [                                     ] 77,948        94.55K/s

13:24:07 (94.27 KB/s) - Read error at byte 77948/15807270 (Connection reset by 
peer). Retrying.

--13:24:08--  http://xxx/example.pdf
  (try: 2) => `example.pdf.29'
Connecting to xxx| xxx |:80... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 15,807,270 (15M), 15,729,322 (15M) remaining [application/pdf]

 3% [>                                    ] 493,221      133.01K/s    ETA 01:52

13:24:11 (132.71 KB/s) - Read error at byte 493221/15807270 (Connection reset 
by peer). Retrying.

--13:24:13--  http://xxx/example.pdf
  (try: 3) => `example.pdf.29'
Connecting to xxx | xxx |:80... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 15,807,270 (15M), 15,314,049 (15M) remaining [application/pdf]

 3% [+                                    ] 581,245      132.67K/s

13:24:14 (132.09 KB/s) - Read error at byte 581245/15807270 (Connection reset 
by peer). Retrying.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to