From: emiddio-verizon <emiddio_at_verizon.net>
Date: Fri, 05 Mar 2010 10:58:51 -0800

i have confirmed the problem; tried to debug it but was unable to locate exactly where the close is occurring so far;

will next use wireshark to see which end is closing first; found gfv3 getting exceptions but was unable to locate where they
1st occurred so far.

i intended to use your servlet -- but remembered i had a short little stand-alone pgm that used HttpURLConnection and could
do a GET; i modified it to add some Thread.sleep(100); to the read loop;

it does not take command line args -- the file to get, and the URL is coded in the pgm.

but its a very little pgm;

i can successfully get the complete file without any sleeps;

but strangely -- if i use Thread.sleep(10 or 20) it will complete without error to the client pgm with a short file in
the 20-40seconds range -- not exactly 30 seconds.

if i use Thread.sleep(100 or 300) -- it seems to run for about 90 seconds +/- some amount -- again with the file
received being shorter than the expected length.

i have not yet been able to solve this problem by debugging --but offer the little program and this info for the community
to consider;

its very easy to use -- just edit the URL, and file to dnload/upload; put a file into domains/domain1/docroot

and play with the Thread.sleep(XXX) values -- with the stock gfv3 i have -- i will get failures to completely dnload/upload a file.

gary