Re: That pesky Amount read didn't match content-length ...
Re: That pesky Amount read didn't match content-length ...
- Subject: Re: That pesky Amount read didn't match content-length ...
- From: Hugi Thordarson via Webobjects-dev <email@hidden>
- Date: Thu, 13 Feb 2025 08:55:57 +0000
Hi OC,
when you say 2 MB, is it possible you mean 2 GB? There used to be (and maybe
still is? it's been a while) a problem with both the Apache adaptor and WO's
own WOAdaptor using an int to keep track of content-length, meaning file
uploads/downloads tended to fail when it was larger than Integer.MAX_VALUE
bytes (~2GB).
Is this also a problem in direct connect mode or only if you're going through
the web server adaptor?
Cheers,
- hugi
> On 12 Feb 2025, at 20:06, ocs--- via Webobjects-dev
> <email@hidden> wrote:
>
> Hi there,
>
> is there a known cure for the darned “IOException: Connection reset by peer:
> Amount read didn't match content-length” exception upon a file upload?
>
> Started to happening to us lately. Smaller files upload all right, bigger
> ones (from about 2 MB up) trigger this error. Increasing the Java memory
> through -Xmx does not seem to help.
>
> Thanks!
> OC
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden