Processing of multipart/form-data request failed. Read timed out
Stan Pinte <[email protected]>
| Newsgroups | gmane.comp.jakarta.commons.user,gmane.text.xml.commons.devel |
|---|---|
| Message-ID | <[email protected]> |
hello, I am using the fileupload component within the struts framework. I have some users having extremely frequently the following problem: INFO | jvm 1 | 2004/06/28 09:51:34 | org.apache.commons.fileupload.FileUploadException: Processing of multipart/form-data request failed. Read timed out I saw that it has already been debated on the list: http://www.mail-archive.com/[email protected]/msg03393.html however, the solution suggested was not to parse the File, if no filename was given. As I am working with struts, the FileUpload is being done earlier in the ~ struts processing: INFO | jvm 1 | 2004/06/28 07:45:50 | org.apache.commons.fileupload.FileUplo adException: Processing of multipart/form-data request failed. Read timed out INFO | jvm 1 | 2004/06/28 07:45:50 | at org.apache.commons.fileupload .FileUpload.parseRequest(FileUpload.java:519) INFO | jvm 1 | 2004/06/28 07:45:50 | at org.apache.commons.fileupload .FileUpload.parseRequest(FileUpload.java:355) INFO | jvm 1 | 2004/06/28 07:45:50 | at org.apache.struts.upload.Comm onsMultipartRequestHandler.handleRequest(CommonsMultipartRequestHandler.java:233 ) INFO | jvm 1 | 2004/06/28 07:45:50 | at org.apache.struts.util.Reques tUtils.populate(RequestUtils.java:1055) INFO | jvm 1 | 2004/06/28 07:45:50 | at org.apache.struts.action.Requ estProcessor.processPopulate(RequestProcessor.java:816) INFO | jvm 1 | 2004/06/28 07:45:50 | at org.apache.struts.action.Requ estProcessor.process(RequestProcessor.java:254) INFO | jvm 1 | 2004/06/28 07:45:50 | at org.apache.struts.action.Acti onServlet.process(ActionServlet.java:1420) INFO | jvm 1 | 2004/06/28 07:45:50 | at org.apache.struts.action.Acti onServlet.doPost(ActionServlet.java:520) INFO | jvm 1 | 2004/06/28 07:45:50 | at javax.servlet.http.HttpServle t.service(HttpServlet.java:760) Any idea why it does occur, and how I could cure it? For me, it sound like a bug in RFC 1867 handling...and it must be at one of two ends: client-side, or server-side. Server-side, the culprit could be the servlet implementation used (Jetty in that case, but the other case uses Tomcat), or FileUpload. An interesting detail: both me and the above cited thread use SSL. would SSL break file uploads? thanks a lot, Stan.