DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=25023>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=25023 ------- Additional Comments From [EMAIL PROTECTED] 2005-06-22 09:13 ------- I guess you are referring to Bug# 31728 in the commons FileUpload project. I took the two latest "nightly builds" from them and included them into my application and it works fine now! How do I know which build fixed this issue? The cvs for FileUploadBase does not mention the revision in which this was fixed. When is the new FileUpload/io release? (In reply to comment #7) > If you're losing 1.5MB per field, then you probably want to check what value > you are specifying for the size threshold for file uploads. My guess is that > it's probably 1.5MB, which is way too big. Configure a much lower value for > this and your memory requirements will drop correspondingly. > This issue is exacerbated by a problem that has subsequently been fixed in > Commons FileUpload / Commons IO. When Struts switches to that, then this issue > will be eased greatly. Since both of those components are pending their 1.1 > releases, the issue remains "Later" for Struts. (In reply to comment #7) > If you're losing 1.5MB per field, then you probably want to check what value > you are specifying for the size threshold for file uploads. My guess is that > it's probably 1.5MB, which is way too big. Configure a much lower value for > this and your memory requirements will drop correspondingly. > This issue is exacerbated by a problem that has subsequently been fixed in > Commons FileUpload / Commons IO. When Struts switches to that, then this issue > will be eased greatly. Since both of those components are pending their 1.1 > releases, the issue remains "Later" for Struts. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
