Yes that is pretty much what I wan't to do, but I seem to be unable to reach this FileUploadException and make sure it is only handled the way I want it to be handled...
------------------------------ Björn Ingimundarson > -----Original Message----- > From: Björn Ingimundarson [mailto:[EMAIL PROTECTED] > Sent: Monday, September 13, 2004 9:34 AM > To: [EMAIL PROTECTED] > Subject: FileUploadException: Stream ended unexpectedly > > > I´m getting this exception in my logs when a user tries to > upload a large > file and cancels by pressing the stop or back button. > > I'm catching this exception in Global Exceptions and just > returning the > user to the upload form, which works fine except I´m still gettin the > exception stack trace in my logs. Now I am trying to clean up > errors in my > system and this is one of the exceptions I would like to get > rid of from > my log files... how do I come about doing this? > > Here's the stack trace: > 16:05:49,456 ERROR > [org.apache.struts.upload.CommonsMultipartRequestHandler.handl > eRequest(CommonsMultipartRequestHandler.java:241)] > Failed to parse multipart request > > org.apache.commons.fileupload.FileUploadException: Processing of > multipart/form-data request failed. Stream ended unexpectedly This is simply saying that the stream ended, which is the case. I would log it as either warn, or info. It's a direct, and correct response by the system to something the user has done. It's also an indicator of potential problems. If the uploads were mission critical I might log as info, or even log to another file and have some daily process go through it and see if there's an abnormally large number of these erorrs. I wouldn't think it serious enough, even for mission critical to eye ball the log every day. YMMV. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ForwardSourceID:NT0001A01E
