FileUploadServlet - Exceeded maximum upload size

[ljm]

Hi -

We are seeing this message repeated in mailbox.log.

2007-08-10 09:33:29,811 INFO [http-443-Processor97] [] FileUploadServlet - Exceeded maximum upload size of 10485760 bytes: org.apache.commons.fileupload.FileUploadBase$SizeL imitExceededException: the request was rejected because it's size exceeds allowed range

355 times since the log rotated at midnight to be exact.

We are also seeing enormous https traffic from a remote site, which has generated signficant excess bandwidth charges over the last few weeks. Here in Australia, bandwidth is charged per Mb.

I've just locked out all the users at the remote site and the bandwidth has dropped off. I am wondering whether perhaps a user has tried to send a really large email via the outlook connector, and then the outlook connector uploads 10Mb, gets a failure from the server and then retries?

It's only a theory, but something along these lines is sure chewing through our bandwidth.

Any thoughts on how to debug this are welcome!

[jholder]

Someone probably has something stuck in their outbox that's too large.

I'd recommend just taking off the limit and letting it pass.
If that's not an option, look in the mailbox.log for a client accessing your server.

[ljm]

Originally Posted by jholder

I'd recommend just taking off the limit and letting it pass.

Yes, experimenting with this now.

The first we knew about this issue was when the ceo asked why excess bandwidth charges were $9,000 last month.

To reduce the likelihood of this happening again, zimbraFileUploadMaxSize will be set high.

But seems like a workaround to the real problem - which is that the outlook connector does an immediate retry and uselessly chews through bandwidth forever.

Maybe the outlook connector needs to know about zimbraFileUploadMaxSize *before* starting the upload?

[ljm]

Just in case anyone else runs into this - the attached shell script was added to /etc/cron.hourly.

[phoenix]

This is a bug and has been resolved in later versions. Please update your profile with your Zimbra version 'zmcontrol -v' will get it.

[ljm]

Our current version:

$ zmcontrol -v

Release 4.5.4_GA_763.RHEL4_20070323121238 CentOS4 NETWORK edition

Great that it's fixed. Do you know whether the fix is in the 4.5 series (latest 4.5.6) or would we be looking at 5.0?

Just to communicate the direct dollar cost impact of this - we're looking at a similar excess bandwidth fee to last month - which accumulated before we understood what was happening.

[phoenix]

This was resolved in 4.5.5.

[TopGear]

I seem to be having the same problem and I have been on 4.5.6 for some time now:

2007-09-25 10:55:47,924 INFO [http-80-Processor92] [name=<<removed email>>;mid=7;ip=71.100.215.80;ua=ZimbraConnectorF orOutlook/0.0;] FileUploadServlet - Exceeded maximum upload size of 10485760 bytes: org.apache.commons.fileupload.FileUploadBase$SizeL imitExceededException: the request was rejected because it's size exceeds allowed range

[zimbra@zimbra root]$ zmcontrol -v
Release 4.5.6_GA_1044.RHEL4_20070706161941 CentOS4 NETWORK edition


Any ideas on why it would still be a problem for me?

[jholder]

Originally Posted by TopGear

I seem to be having the same problem and I have been on 4.5.6 for some time now:

2007-09-25 10:55:47,924 INFO [http-80-Processor92] [name=<<removed email>>;mid=7;ip=71.100.215.80;ua=ZimbraConnectorF orOutlook/0.0;] FileUploadServlet - Exceeded maximum upload size of 10485760 bytes: org.apache.commons.fileupload.FileUploadBase$SizeL imitExceededException: the request was rejected because it's size exceeds allowed range

[zimbra@zimbra root]$ zmcontrol -v
Release 4.5.6_GA_1044.RHEL4_20070706161941 CentOS4 NETWORK edition


Any ideas on why it would still be a problem for me?

Hi-
Please upgrade to the latest version of Zimbra (4.5.7) and see if you get the same error.

Best,
john