Return-Path: Delivered-To: apmail-commons-issues-archive@locus.apache.org Received: (qmail 62040 invoked from network); 27 Oct 2007 16:42:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Oct 2007 16:42:15 -0000 Received: (qmail 78821 invoked by uid 500); 27 Oct 2007 16:42:01 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 78767 invoked by uid 500); 27 Oct 2007 16:42:01 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 78758 invoked by uid 99); 27 Oct 2007 16:42:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Oct 2007 09:42:01 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Oct 2007 16:42:16 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 8BF5C714240 for ; Sat, 27 Oct 2007 09:41:50 -0700 (PDT) Message-ID: <28660547.1193503310563.JavaMail.jira@brutus> Date: Sat, 27 Oct 2007 09:41:50 -0700 (PDT) From: "Jochen Wiedmann (JIRA)" To: issues@commons.apache.org Subject: [jira] Commented: (FILEUPLOAD-149) Intermittent file corruption on upload In-Reply-To: <10953473.1193244530599.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/FILEUPLOAD-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538226 ] Jochen Wiedmann commented on FILEUPLOAD-149: -------------------------------------------- I studied the mail from F. Andy Seidl you are quoting and I must admit that I simply don't believe it. If the problems were as extreme as he states (no successful upload at all), then commons fileupload would be completely useless. Which it is not, because quite a lot of people use it in the wild. > Intermittent file corruption on upload > -------------------------------------- > > Key: FILEUPLOAD-149 > URL: https://issues.apache.org/jira/browse/FILEUPLOAD-149 > Project: Commons FileUpload > Issue Type: Bug > Affects Versions: 1.2 > Environment: Linux (CentOS) server; all client platforms and browsers > Reporter: F. Andy Seidl > Priority: Critical > > I have been struggling for several weeks trying to track down the root cause > of a sporadic file corruption problem using File Upload. I'm really stumped > at this point and welcome any suggestions as to avenues of debugging > pursuit. > Here's overview of the problem: > I have eight Linux (CentOS) servers all running the same web application--a > set of Java servlets using Resin as a servlet runner under Apache. All > servers were configured using the same script that installs jars, > config files, etc. > On three of the servers, File Upload works reliably. On five of the > servers, File Upload usually (but not always) leaves me with a corrupted file. > Corrupted files are always the correct length but contain a relatively small > percentage of scrambled bytes. I looked for obvious patterns like newlines > being altered or high-bit bytes being converted to or from UTF-8, but there > is no obvious (to me, anyway) pattern in the failure. > I have also tested with IE, FireFox, and Safari on both Windows and MacOS. > The issue appears to be independent of client browser and OS. > Looking at Java system properties, I notice that while the classpath and > bootclasspath have the same jars lists on all servers, they are not listed > in the same order (probably listed in directory order as the paths are > constructed by a script that inspects lib directories.) > Is anyone aware of classpath order dependencies that could break File > Upload? > Can anyone offer any suggestions about what *might* be breaking File Upload? > Or what other questions I should be asking? At the moment, I'm feeling > rather stumped. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.