Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 91432 invoked from network); 8 Jan 2009 22:14:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Jan 2009 22:14:09 -0000 Received: (qmail 20586 invoked by uid 500); 8 Jan 2009 22:13:58 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 20297 invoked by uid 500); 8 Jan 2009 22:13:57 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 20286 invoked by uid 99); 8 Jan 2009 22:13:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jan 2009 14:13:57 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [74.54.141.23] (HELO mail.writingshow.com) (74.54.141.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jan 2009 22:13:48 +0000 Received: from cpe-98-149-75-20.socal.res.rr.com ([98.149.75.20] helo=[192.168.1.106]) by mail.writingshow.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.67) (envelope-from ) id 1LL3EV-0004GD-Vj for users@tomcat.apache.org; Thu, 08 Jan 2009 16:20:08 -0600 Message-ID: <49667A85.50702@compulsivecreative.com> Date: Thu, 08 Jan 2009 14:13:25 -0800 From: Alan Chaney Reply-To: alan@compulsivecreative.com Organization: Paula Hollywood, Inc. User-Agent: Thunderbird 1.5.0.14ubu (X11/20080505) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: File upload fails References: <21360958.post@talk.nabble.com> <49666FE6.1060804@compulsivecreative.com> <21361472.post@talk.nabble.com> In-Reply-To: <21361472.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org javacle wrote: > The file is about 30Mbytes > .. I get the same error uploading from the office on the same LAN as the > server. Ok - not likely to be a problem with the remote connection, then. What do you see in your browser when the upload fails? Have you got any browser debugging - if you are using Firefox you can easily add the 'LiveHttpHeaders' plugin which I find very useful. What happens inside your application following the upload? Is there a significant period of processing in the same thread as the servlet doGet? If so, its possible that your connection is timing out. As you can simulate the problem in your office, what happens if you DON'T restart tomcat after you get the connection issue? If you just leave it for a little while can you then upload again? > Browser is (I think) always MSIE 6 .. but maybe sometimes Mozilla .. that's > something to check. > I will look into wireshark. Having a monitor on the connection will be useful. You should be able to install wireshark from your distro. I assume that as you are using MSIE then your dev. system is a PC? I develop on linux and don't know of any particular network monitor to recommend. HTH Alan > > > > Alan Chaney wrote: >> How big is the file? >> >> "Connection reset" is commonly caused by the the client dropping the >> connection. This could be because of connectivity problems - for >> example, issues with the clients ISP. >> >> I have had problems with specific browsers over this as well (our site >> has dozens of large mpeg and jpeg uploads each day). The worst culprit >> proved to be Safari 3 on a Mac. Is the upload done with SSL? >> >> I doubt that restarting the server makes any difference one way or the >> other. Why not get the client to test with a non-urgent file and a >> non-urgent time when you have a chance to fault-find? Also, you may >> want to watch the upload with something like wireshark to see exactly >> what is happening and when. >> >> Regards >> >> Alan Chaney >> >> >> javacle wrote: >>>

We have a customer who uploads a file on a daily basis. >>> Usually it works, but about once every two weeks it fails with this error >>> in >>> the log : >>>

org.apache.commons.fileupload.FileUploadException: Processing of >>> multipart/form-data request failed. Connection reset >>>

After restarting tomcat, sometimes three times, it eventually works. >>> Whether the restarting is significant or just the passage of time that >>> clears some other fault I dont know .. there is always a panic to get it >>> working >>> >>>

The customer is on the other side of the continent, but today she >>> emailed >>> the file to me and I had the same error trying to upload her file from >>> the >>> office the first time (i.e. same building as server). So that would seem >>> to >>> eliminate long-distance network latency/timeout as a factor. >>> >>>

Nothing I am aware of has changed since the last time it worked, >>> however >>> something may have changed in the network, or on the server, without >>> being >>> noticed. >>> >>> Any advice would be appreciated >>> >>> tomcat 5.5, jre 1.4.2, Red Hat Enterprise Linux ES release 4 (Nahant) >>> Kernel >>> 2.6.9-5.ELsmp on an i686 >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org >> For additional commands, e-mail: users-help@tomcat.apache.org >> >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org