You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Caldarale, Charles R" <Ch...@unisys.com> on 2009/05/22 00:15:33 UTC
RE: Upload stop after 30 minutes: Processing of multipart/form-data
requestfailed. Stream ended unexpectedly
> From: Patrick Herber [mailto:patrick.herber@ticino.com]
> Subject: Upload stop after 30 minutes: Processing of multipart/form-
> data requestfailed. Stream ended unexpectedly
>
> I'm experiencing problems uploading big files on it: after around 30
> minutes (nearly exactly 30 minutes!) the upload stops.
What happens if you go directly into port 8080, bypassing httpd?
I realize it shouldn't have anything to do with the session timeout (and your AJAX requests should be resetting the timer), but that's the only thing I can think of in Tomcat that has a default value of 30 minutes. Just for grins, what happens if you change that to 60? Or 10?
Is there anything in between httpd and Tomcat (e.g., firewall) that might be dropping the connection?
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
requestfailed. Stream ended unexpectedly
Posted by will trillich <tr...@gmail.com>.
On Fri, May 22, 2009 at 2:22 PM, Christopher Schultz
<ch...@christopherschultz.net> wrote:
> On 5/22/2009 2:01 PM, will trillich wrote:
>> - we'd accidentally set up 'default gateway' on both
>>
>> This meant the system was confused as to where to send replies.
>
> I recently had a sever misconfiguration in a slightly different way: the
> default route was set to use an eth device that wasn't physically
> connected to anything, and the server's primary IP address was also
> bound to that device.
>
> The symptoms were that no outgoing connections could be made
> successfully, but that incoming connections worked just fine.
>
> This was on a Linux 2.4 kernel, which appears to route the replies
> without a problem even with such an egregious misconfiguration: the
> kernel appeared to be smart enough to send replies to the "right place"
> regardless of the stupidity of the configuration.
>
> In what environment did this default route misconfiguration cause
> unreliable responses?
Windo~1 2003 Enterprise.
It was really weird. For hours at a time, all was well. Packets came,
packets went. Pages were browsed. Then -- poof! -- no traffic at all.
We were originally thinking it was another computer with the same IP
address that had no server, getting all the traffic.
Nope. Just too many default gateways. :)
--
will trillich
"Our only real economic security lies in our power to meet human
needs." -- S.Covey, the 8th Habit
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
requestfailed. Stream ended unexpectedly
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Will,
On 5/22/2009 2:01 PM, will trillich wrote:
> Hmm. This sounds kinda like something we ran into lately -- maybe this
> will help you:
> - our server had TWO nic cards, one for internal 10.10.*.* one for
> external 208.*.*.*
> - we'd accidentally set up 'default gateway' on both
>
> This meant the system was confused as to where to send replies.
I recently had a sever misconfiguration in a slightly different way: the
default route was set to use an eth device that wasn't physically
connected to anything, and the server's primary IP address was also
bound to that device.
The symptoms were that no outgoing connections could be made
successfully, but that incoming connections worked just fine.
This was on a Linux 2.4 kernel, which appears to route the replies
without a problem even with such an egregious misconfiguration: the
kernel appeared to be smart enough to send replies to the "right place"
regardless of the stupidity of the configuration.
In what environment did this default route misconfiguration cause
unreliable responses?
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkoW+5MACgkQ9CaO5/Lv0PAIZACgwGFY2HpaUbGUg99CRrS3RGtj
S5MAnjyriSd0OZm/lEbBnLr+bQmP6uHA
=MOIv
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by Patrick Herber <pa...@ticino.com>.
> ProxyTimeout 3600
> This looks a lot like 30min ;)
IMHO no... it should be 60 seconds * 60 = 1 hour
Regards
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: André Warnier [mailto:aw@ice-sa.com]
> Subject: Re: Upload stop after 30 minutes: Processing of
> multipart/form-data request failed. Stream ended unexpectedly
>
> All in all, I believe the on-line doc has a bigger chance of being
> accurate than the book; and I also believe Tomcat will just ignore
> attributes that it does not know.
Correct on both counts.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by Martin Gainty <mg...@hotmail.com>.
any way to incorporate Javadoc AND translations as part of the build for
deutsche?
francais?
polska?
italiano?
norsk?
svenska?
BTW: andre you are awake now so looks like you are one of the early am TC gurus
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
> Date: Wed, 5 Aug 2009 14:01:55 +0200
> From: aw@ice-sa.com
> To: users@tomcat.apache.org
> Subject: Re: Upload stop after 30 minutes: Processing of multipart/form-data request failed. Stream ended unexpectedly
>
> Mateusz Kijowski wrote:
> > 2009/8/4 André Warnier <aw...@ice-sa.com>:
> >> May or may not be relevant, but I do not see the above attributes in the
> >> Tomcat AJP Connector docs.
> >> http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html
> >> and only see disableUploadTimeout in the HTTP Connector.
> >> http://tomcat.apache.org/tomcat-6.0-doc/config/http.html
> >
> > André,
> >
> >
> > Thanks for your reply. Those attributes are taken from polish
> > translation of "Tomcat. The definitive guide." from O'Reilly. Perhaps
> > the on-line docs are out of date? Tomcat doesn't complain about them
> > at startup so I suppose that they are correct. Moreover, I added those
> > hoping that it would solve the issue so these are most probably not
> > causing my problems.
> >
> The experts should be waking up soon, and they will tell us.
> All in all, I believe the on-line doc has a bigger chance of being
> accurate than the book; and I also believe Tomcat will just ignore
> attributes that it does not know.
>
> In which case you are right, they would not be causing your problem. But
> they may give you the impression that you are changing something, while
> you aren't.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
_________________________________________________________________
Get your vacation photos on your phone!
http://windowsliveformobile.com/en-us/photos/default.aspx?&OCID=0809TL-HM
Re: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by Mark Thomas <ma...@apache.org>.
Mateusz Kijowski wrote:
>>> All in all, I believe the on-line doc has a bigger chance of being
>>> accurate than the book; and I also believe Tomcat will just ignore
>>> attributes that it does not know.
>> I regard both of the above statements as true. What version of Tomcat
>> does your copy of "Tomcat: The Definitive Guide" cover? Assuming you
>> have the 2nd Edition, it was written in 2007 and should cover Tomcat 6
>> configuration as well as 5.5.
>
> The "Definitive Guide" I have is the second edition, supposedly
> covering 6.0. The book doesn't describe HTTP and AJP connectors
> separately, instead the attributes in question are both present in the
> list of allowed attributes for the Connector config element.
That is bad. There are significant differences between AJP and HTTP.
> The
> header of the attribute list says that the list contains attributes
> allowed by all Connectors shipped with Tomcat (not specifying any
> specific version). That's why I guessed that Tomcat version was
> irrelevant.
>
> Again, either the on-line docs are out of date, or the book is wrong.
The book is wrong. Whilst the on-line docs aren't perfect they are
always going to be more up to date than a book.
>> You didn't mention which version of Tomcat you're using, so we don't
>> know which configuration documentation to send you. :(
>
> Sorry about that, I am using 6.0.18 and Apache httpd 2.2.11. The
> problem still occurs quite regularly, and I can't think of any more
> settings to tune.
As per the advice previously mentioned in this thread. Connect directly
to Tomcat and see if you still get the problem. That would help narrow
things down.
What is your timeout setting for httpd?
Personally, I usually roll out Wireshark / tcpdump at this point to see
exactly what is going on. It'll be a time-out somewhere. You just need
to find out where.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by Mateusz Kijowski <ma...@gmail.com>.
>> All in all, I believe the on-line doc has a bigger chance of being
>> accurate than the book; and I also believe Tomcat will just ignore
>> attributes that it does not know.
>
> I regard both of the above statements as true. What version of Tomcat
> does your copy of "Tomcat: The Definitive Guide" cover? Assuming you
> have the 2nd Edition, it was written in 2007 and should cover Tomcat 6
> configuration as well as 5.5.
The "Definitive Guide" I have is the second edition, supposedly
covering 6.0. The book doesn't describe HTTP and AJP connectors
separately, instead the attributes in question are both present in the
list of allowed attributes for the Connector config element. The
header of the attribute list says that the list contains attributes
allowed by all Connectors shipped with Tomcat (not specifying any
specific version). That's why I guessed that Tomcat version was
irrelevant.
Again, either the on-line docs are out of date, or the book is wrong.
> You didn't mention which version of Tomcat you're using, so we don't
> know which configuration documentation to send you. :(
Sorry about that, I am using 6.0.18 and Apache httpd 2.2.11. The
problem still occurs quite regularly, and I can't think of any more
settings to tune.
Thanks for all of your replies,
Mateusz.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
André,
On 8/5/2009 8:01 AM, André Warnier wrote:
> All in all, I believe the on-line doc has a bigger chance of being
> accurate than the book; and I also believe Tomcat will just ignore
> attributes that it does not know.
I regard both of the above statements as true. What version of Tomcat
does your copy of "Tomcat: The Definitive Guide" cover? Assuming you
have the 2nd Edition, it was written in 2007 and should cover Tomcat 6
configuration as well as 5.5.
You didn't mention which version of Tomcat you're using, so we don't
know which configuration documentation to send you. :(
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkp5ik4ACgkQ9CaO5/Lv0PDP6ACfQMKnvV4og2eBeV6oN4CkQePv
0s8AoIf8jXo4Ip2SZE5KVtDh+a7ARPA6
=H3zz
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by André Warnier <aw...@ice-sa.com>.
Mateusz Kijowski wrote:
> 2009/8/4 André Warnier <aw...@ice-sa.com>:
>> May or may not be relevant, but I do not see the above attributes in the
>> Tomcat AJP Connector docs.
>> http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html
>> and only see disableUploadTimeout in the HTTP Connector.
>> http://tomcat.apache.org/tomcat-6.0-doc/config/http.html
>
> André,
>
>
> Thanks for your reply. Those attributes are taken from polish
> translation of "Tomcat. The definitive guide." from O'Reilly. Perhaps
> the on-line docs are out of date? Tomcat doesn't complain about them
> at startup so I suppose that they are correct. Moreover, I added those
> hoping that it would solve the issue so these are most probably not
> causing my problems.
>
The experts should be waking up soon, and they will tell us.
All in all, I believe the on-line doc has a bigger chance of being
accurate than the book; and I also believe Tomcat will just ignore
attributes that it does not know.
In which case you are right, they would not be causing your problem. But
they may give you the impression that you are changing something, while
you aren't.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by Mateusz Kijowski <ma...@gmail.com>.
2009/8/4 André Warnier <aw...@ice-sa.com>:
> May or may not be relevant, but I do not see the above attributes in the
> Tomcat AJP Connector docs.
> http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html
> and only see disableUploadTimeout in the HTTP Connector.
> http://tomcat.apache.org/tomcat-6.0-doc/config/http.html
André,
Thanks for your reply. Those attributes are taken from polish
translation of "Tomcat. The definitive guide." from O'Reilly. Perhaps
the on-line docs are out of date? Tomcat doesn't complain about them
at startup so I suppose that they are correct. Moreover, I added those
hoping that it would solve the issue so these are most probably not
causing my problems.
Does anybody have any other suggestions? Thanks in advance,
Mateusz.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by christianjunk <ch...@christianjunk.de>.
Is there any solution out now? I'm having the same problems with Tomcat
6.0.18 (Windows) behind an Apache2 webserver, using ProxyPass.
When I connect to Tomcat directly I have no problems and the uploads work
fine.
Regards,
Christian
--
View this message in context: http://www.nabble.com/Upload-stop-after-30-minutes%3A-Processing-of-multipart-form-data-request-failed.-Stream-ended-unexpectedly-tp23660524p25958247.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chuck,
On 8/5/2009 9:42 AM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:chris@christopherschultz.net]
>> Subject: Re: Upload stop after 30 minutes: Processing of
>> multipart/form-data request failed. Stream ended unexpectedly
>>
>> disableUploadTimeout is definitely in the HTTP connector
>> documentation.
>
> True, but we're talking about the AJP, not HTTP, connector, and
> there's no tag in the docs related to upload timeouts for AJP.
Right: I was just pointing out that disableUploadTimeout is at least
relevant /somewhere/, while the other settings seems to be either
fictional or a misprint.
I even checked Tomcat 4.1 (my alma mater), and connectionUploadTimeout
just ain't there.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkp5xIUACgkQ9CaO5/Lv0PA+eACfZIa1s6bxSyEDS3GvrBwQe3xH
Q9YAnRYQcpu8Zz9Ncn3bbG94nIPiNH36
=/Fdi
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Christopher Schultz [mailto:chris@christopherschultz.net]
> Subject: Re: Upload stop after 30 minutes: Processing of
> multipart/form-data request failed. Stream ended unexpectedly
>
> disableUploadTimeout is definitely in the HTTP connector documentation.
True, but we're talking about the AJP, not HTTP, connector, and there's no tag in the docs related to upload timeouts for AJP.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
Re: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
André,
On 8/4/2009 3:04 PM, André Warnier wrote:
> Mateusz Kijowski wrote:
>>
>> <Connector port="8009"
>>
> ...
>> connectionUploadTimeout="3600000"
>> disableUploadTimeout="true"
>>
> ...
> May or may not be relevant, but I do not see the above attributes in the
> Tomcat AJP Connector docs.
disableUploadTimeout is definitely in the HTTP connector documentation.
The other one does not appear in the 6.0 documentation.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkp5iz4ACgkQ9CaO5/Lv0PBAsQCeKAykTalI9QPSoC8/6B4oRo0N
alwAoJ0fpGfHUg3tE31DVfr0mys6H820
=xmPy
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by André Warnier <aw...@ice-sa.com>.
Mateusz Kijowski wrote:
>
> <Connector port="8009"
>
...
> connectionUploadTimeout="3600000"
> disableUploadTimeout="true"
>
...
May or may not be relevant, but I do not see the above attributes in the
Tomcat AJP Connector docs.
http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html
and only see disableUploadTimeout in the HTTP Connector.
http://tomcat.apache.org/tomcat-6.0-doc/config/http.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by Mateusz Kijowski <ma...@gmail.com>.
Hi,
It seems that I am encountering the same or similar problem. I am
getting the same exception using the same proxy setup (Apache httpd ->
mod_proxy_ajp -> AJP Connector -> Apache Tomcat), although I am not
certain that the exception occurs after 30 minutes. The only way to
reproduce this error involved using bandwidth throttler on a Windows
XP client. It also seems that the problem is reproducible only under
IE, but I might be wrong about this. I tried to reproduce the error by
modifying various timeouts, but I did not succeed.
Below are relevant configuration snippets:
<Connector port="8009"
protocol="AJP/1.3" connectionTimeout="120000" maxThreads="1000"
minSpareThreads="50" maxSpareThreads="100" enableLookups="false"
acceptCount="150" address="127.0.0.1"
useBodyEncodingForURI="true"
compression="on"
compressionMinSize="1024"
compressableMimeType="text/html,text/xml"
connectionUploadTimeout="3600000"
disableUploadTimeout="true"
/>
Timeout 600
<VirtualHost example.com>
#[...]
Timeout 3600
ProxyPass / ajp://localhost:8009/
ProxyPassReverse / ajp://localhost:8009/
ProxyTimeout 3600
</VirtualHost>
Patrick, did you manage to find the cause? Does anyone else have a
hint what might be the cause?
Thanks for your help,
Mateusz.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by Patrick Herber <pa...@ticino.com>.
Originally I'd put this setting ProxyTimeout 3600, because it seams to
be the only existing timeout setting at proxy's level (togheter with
Timeout and the attribute timeout=xxx of proxypass).
However, removing this setting, putting it after ProxyPass, using
Timeout at VirtualHost level (see:
http://mail-archives.apache.org/mod_mbox/httpd-users/200710.mbox/%3C20071003101352.GA9810@w032y7.pnet.ch%3E)
does not make any difference...
Do you have any other suggestions?
Thanks a lot again for your help.
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Upload stop after 30 minutes: Processing of
multipart/form-datarequest failed. Stream ended unexpectedly
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: André Warnier [mailto:aw@ice-sa.com]
> Subject: Re: Upload stop after 30 minutes: Processing of
> multipart/form-datarequest failed. Stream ended unexpectedly
>
> Bill Barker wrote:
>
> >> ProxyTimeout 3600
> >
> > This looks a lot like 30min ;)
> >
> Does it really ?
Maybe he was moving at 0.75c at the time... it's all relative.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by André Warnier <aw...@ice-sa.com>.
Bill Barker wrote:
>> ProxyTimeout 3600
>
> This looks a lot like 30min ;)
>
Does it really ?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: news [mailto:news@ger.gmane.org] On Behalf Of Bill Barker
> Subject: Re: Upload stop after 30 minutes: Processing of
> multipart/form-data request failed. Stream ended unexpectedly
>
> > <IfModule mod_proxy_ajp.c>
> > ProxyRequests Off
> > ProxyTimeout 3600
>
> This looks a lot like 30min ;)
??? Isn't that more like 60 minutes?
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data request failed. Stream ended unexpectedly
Posted by Bill Barker <wb...@wilshire.com>.
"Patrick Herber" <pa...@ticino.com> wrote in message
news:4A19B564.8030804@ticino.com...
> Hello
>
> I've made some more tests and after reading the Book "*Tomcat, The
> definitive Guide*" I discovered the existence of a parameter called
> "*connectionUploadTimeout*" (below I join the description of this
> property taken from this book).
> I've changed the configuration of the HTTP connector and now uploading
> big files directly on tomcat (without Apache HTTP) works without problems:
>
> <Connector port="80" protocol="HTTP/1.1"
> connectionTimeout="600000"
> connectionUploadTimeout="3600000"
> disableUploadTimeout="true"
> redirectPort="8443" />
>
> However, if I reset our original configuration with Tomcat behind an
> Apache HTTP connected with mod_proxy_ajp (or mod_proxy_http) I get the
> same Exception as before (the Upload stops after 30 minutes).
>
> <IfModule mod_proxy_ajp.c>
> ProxyRequests Off
> ProxyTimeout 3600
This looks a lot like 30min ;)
> <Location / >
> ProxyPass ajp://localhost:8009/
> ProxyPassReverse ajp://localhost:8009/
> </Location>
> </IfModule>
>
> <Connector port="8009" protocol="AJP/1.3"
> connectionTimeout="600000"
> connectionUploadTimeout="3600000"
> disableUploadTimeout="true"
> redirectPort="8443" />
>
> Or
>
> <IfModule mod_proxy_http.c>
> ProxyRequests Off
> ProxyTimeout 3600
> <Location / >
> ProxyPass http://localhost:8080/
> ProxyPassReverse http://localhost:8080/
> </Location>
> </IfModule>
>
> <Connector port="8080" protocol="HTTP/1.1"
> connectionTimeout="600000"
> connectionUploadTimeout="3600000"
> disableUploadTimeout="true"
> redirectPort="8443" />
>
> I've tried setting the "timeout" parameter in the ProxyPass instruction
> to one hour:
>
> ProxyPass ajp://localhost:8009/ timeout=3600
>
> But it did not help...
> Do you have any suggestion?
>
> Thanks a lot for your attention and your help
> Patrick
>
>
> Here the description of the three properties copied from the Book
> "Tomcat, The definitive Guide" (O'Reilly, Jason Brittain with Ian F.
> Darwin). I missed these information in the official Tomcat documentation
> (didn't I see it?):
>
> *disableUploadTimeout*
> Should Tomcat use the regular connectionTimeout for request socket
> connections even for long servlet requests, such as uploads? Setting
> disableUploadTimeout to true allows long requests to servlets to
> continue without the Connector closing the connection. Setting it to
> false means that a longer connection timeout (connectionUploadTimeout's
> value) will be used for requests to servlets. Setting it to false means
> that the lower connection timeout specified in the connectionTimeout
> attribute will be applied to all types of requests.
> The default for this attribute is not consistent between Connector
> implementations and versions of Tomcat. We strongly suggest that you
> explicitly set it to either true or false.
>
> *connectionTimeout*
> The Connector may wait a configurable number of milliseconds from the
> time the client's request TCP socket is accepted until the request
> method line is sent to Tomcat.
> The default is 1 minute. 60000
>
> *connectionUploadTimeout*
> By default, Connectors keep request socket connections open while Tomcat
> processes the request, until the connectionTimeout of 1 minute has
> passed. At that point, the Connector will close the socket. But, this
> causes trouble if the request was for a long running servlet, such as a
> file upload. During requests that map to servlets, Tomcat will use a
> longer timeout, specified by the connectionUploadTimeout attribute in
> milliseconds.
> The default is 300000 milliseconds (5 minutes). 300000
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
request failed. Stream ended unexpectedly
Posted by Patrick Herber <pa...@ticino.com>.
Hello
I've made some more tests and after reading the Book "*Tomcat, The
definitive Guide*" I discovered the existence of a parameter called
"*connectionUploadTimeout*" (below I join the description of this
property taken from this book).
I've changed the configuration of the HTTP connector and now uploading
big files directly on tomcat (without Apache HTTP) works without problems:
<Connector port="80" protocol="HTTP/1.1"
connectionTimeout="600000"
connectionUploadTimeout="3600000"
disableUploadTimeout="true"
redirectPort="8443" />
However, if I reset our original configuration with Tomcat behind an
Apache HTTP connected with mod_proxy_ajp (or mod_proxy_http) I get the
same Exception as before (the Upload stops after 30 minutes).
<IfModule mod_proxy_ajp.c>
ProxyRequests Off
ProxyTimeout 3600
<Location / >
ProxyPass ajp://localhost:8009/
ProxyPassReverse ajp://localhost:8009/
</Location>
</IfModule>
<Connector port="8009" protocol="AJP/1.3"
connectionTimeout="600000"
connectionUploadTimeout="3600000"
disableUploadTimeout="true"
redirectPort="8443" />
Or
<IfModule mod_proxy_http.c>
ProxyRequests Off
ProxyTimeout 3600
<Location / >
ProxyPass http://localhost:8080/
ProxyPassReverse http://localhost:8080/
</Location>
</IfModule>
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="600000"
connectionUploadTimeout="3600000"
disableUploadTimeout="true"
redirectPort="8443" />
I've tried setting the "timeout" parameter in the ProxyPass instruction
to one hour:
ProxyPass ajp://localhost:8009/ timeout=3600
But it did not help...
Do you have any suggestion?
Thanks a lot for your attention and your help
Patrick
Here the description of the three properties copied from the Book
"Tomcat, The definitive Guide" (O'Reilly, Jason Brittain with Ian F.
Darwin). I missed these information in the official Tomcat documentation
(didn't I see it?):
*disableUploadTimeout*
Should Tomcat use the regular connectionTimeout for request socket
connections even for long servlet requests, such as uploads? Setting
disableUploadTimeout to true allows long requests to servlets to
continue without the Connector closing the connection. Setting it to
false means that a longer connection timeout (connectionUploadTimeout's
value) will be used for requests to servlets. Setting it to false means
that the lower connection timeout specified in the connectionTimeout
attribute will be applied to all types of requests.
The default for this attribute is not consistent between Connector
implementations and versions of Tomcat. We strongly suggest that you
explicitly set it to either true or false.
*connectionTimeout*
The Connector may wait a configurable number of milliseconds from the
time the client's request TCP socket is accepted until the request
method line is sent to Tomcat.
The default is 1 minute. 60000
*connectionUploadTimeout*
By default, Connectors keep request socket connections open while Tomcat
processes the request, until the connectionTimeout of 1 minute has
passed. At that point, the Connector will close the socket. But, this
causes trouble if the request was for a long running servlet, such as a
file upload. During requests that map to servlets, Tomcat will use a
longer timeout, specified by the connectionUploadTimeout attribute in
milliseconds.
The default is 300000 milliseconds (5 minutes). 300000
Re: Upload stop after 30 minutes: Processing of multipart/form-data
requestfailed. Stream ended unexpectedly
Posted by will trillich <tr...@gmail.com>.
Hmm. This sounds kinda like something we ran into lately -- maybe this
will help you:
- our server had TWO nic cards, one for internal 10.10.*.* one for
external 208.*.*.*
- we'd accidentally set up 'default gateway' on both
This meant the system was confused as to where to send replies. Looked
like a firewall issue, a router issue... but it was just a
mis-configuration in the network settings. Ports didn't matter,
firewall was okay, router couldn't get a dependable response...
E.G. if your IPs are 10.10.10.10/255.255.0.0 and
1.2.3.4/255.255.255.240 then your network knows which interface a
packed aimed at 10.10.1.1 should go out on, or where a packet aimed at
1.2.3.7 should go out on. But where would a packet aimed at
222.222.222.222 go? That's when you have a default gateway, which in
this case would probably be something like 1.2.3.1.
In case this helps.
On Fri, May 22, 2009 at 7:13 AM, Patrick Herber
<pa...@ticino.com> wrote:
> Thanks a lot for your reply!
>
> I've tried your suggestions this are the results.
>
>> What happens if you go directly into port 8080, bypassing httpd?
> I've tried but I get the same exception
>
>> Just for grins, what happens if you change that to 60? Or 10?
> I've tried but nothing has changed...
>
>> Is there anything in between httpd and Tomcat (e.g., firewall) that might
>> be dropping the connection?
> No (and now that I've tested directly on tomcat I presume that it's either a
> Tomcat or a Commons FileUpload configuration problem)
>
> Looking after the problem I also found a suggestion to explicity set
> "disableUploadTimeout to false" (see
> http://www.tek-tips.com/viewthread.cfm?qid=627123): I've also tried this one
> but without success...
>
> Any other suggestion?
>
> Thanks a lot again for your help
>
> Patrick
>
>>> From: Patrick Herber [mailto:patrick.herber@ticino.com]
>>> Subject: Upload stop after 30 minutes: Processing of multipart/form-
>>> data requestfailed. Stream ended unexpectedly
>>>
>>> I'm experiencing problems uploading big files on it: after around 30
>>> minutes (nearly exactly 30 minutes!) the upload stops.
>>>
>>
>> What happens if you go directly into port 8080, bypassing httpd?
>>
>> I realize it shouldn't have anything to do with the session timeout (and
>> your AJAX requests should be resetting the timer), but that's the only thing
>> I can think of in Tomcat that has a default value of 30 minutes. Just for
>> grins, what happens if you change that to 60? Or 10?
>>
>> Is there anything in between httpd and Tomcat (e.g., firewall) that might
>> be dropping the connection?
>>
>> - Chuck
>>
>>
>> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
>> MATERIAL and is thus for use only by the intended recipient. If you received
>> this in error, please contact the sender and delete the e-mail and its
>> attachments from all computers.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>
--
will trillich
"Our only real economic security lies in our power to meet human
needs." -- S.Covey, the 8th Habit
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Upload stop after 30 minutes: Processing of multipart/form-data
requestfailed. Stream ended unexpectedly
Posted by Patrick Herber <pa...@ticino.com>.
Thanks a lot for your reply!
I've tried your suggestions this are the results.
> What happens if you go directly into port 8080, bypassing httpd?
I've tried but I get the same exception
> Just for grins, what happens if you change that to 60? Or 10?
I've tried but nothing has changed...
> Is there anything in between httpd and Tomcat (e.g., firewall) that
might be dropping the connection?
No (and now that I've tested directly on tomcat I presume that it's
either a Tomcat or a Commons FileUpload configuration problem)
Looking after the problem I also found a suggestion to explicity set
"disableUploadTimeout to false" (see
http://www.tek-tips.com/viewthread.cfm?qid=627123): I've also tried this
one but without success...
Any other suggestion?
Thanks a lot again for your help
Patrick
>> From: Patrick Herber [mailto:patrick.herber@ticino.com]
>> Subject: Upload stop after 30 minutes: Processing of multipart/form-
>> data requestfailed. Stream ended unexpectedly
>>
>> I'm experiencing problems uploading big files on it: after around 30
>> minutes (nearly exactly 30 minutes!) the upload stops.
>>
>
> What happens if you go directly into port 8080, bypassing httpd?
>
> I realize it shouldn't have anything to do with the session timeout (and your AJAX requests should be resetting the timer), but that's the only thing I can think of in Tomcat that has a default value of 30 minutes. Just for grins, what happens if you change that to 60? Or 10?
>
> Is there anything in between httpd and Tomcat (e.g., firewall) that might be dropping the connection?
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>