What makes everyone so certain it's not a bug or multiple bugs? Since you don't get stack traces and at best can pin down the thread name for OutOfMemoryErrors, they take a lot of time to track down. In my experience, though, they tend to result from an unaccounted for degenerate request coming that causes the code to, well, consume all the available memory (i.e., a bug).
-Adam
Shapira, Yoav wrote:
Howdy, This belongs on the user, not dev, list. It's most likely a simple issue (not a bug) with you not allocating enough memory to the JVM. Please pursue this issue on the user list.
Yoav Shapira Millennium ChemInformatics
-----Original Message----- From: Fabrizio Nesti [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 1:35 PM To: [EMAIL PROTECTED] Subject: Any clue on this, please? Uploading large files - out of
memory
Hi, any comment on this "out of memory" with large file upload?
This error seems recurring to a bunch of users, but I'm wondering if
it's a
problem in the tomcat implementation, or if there are other layers to blame.
Thanks for any light on this darkness, since I've a tight schedule on this issue... unfortunately.. cheers, fabrizio
---------- Forwarded message ---------- Date: Mon, 1 Dec 2003 14:36:57 +0100 (MET) From: Fabrizio Nesti <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Uploading large files - out of memory exception
Dear tomcat developers,
I've noticed a problem while uploading files with tomcat 4.1.x.
- When uploading large files (say larger than 10MB) tomcat throws an
out
of memory exception.
- The problem can be avoided raising the memory allocation (as found in other similar messages, -Xms128m -Xmx512m) but this is not a
solution,
since it depends on the memory and just makes the limit higher.
I do not know how the actual download works (we are using the EchoPoint fileupload component, for that matters) but it seems that the whole file is slurped in memory _before_ passing the request to a user servlet. Indeed it seems that our download component is never invoked (see the error below).
Is there a configuration option to avoid this behavior, or there's nothing to do but limit the filesize?
Thanks in advance for any clue and cheers, Fabrizio
PS: The error:
... description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applic
atio
nFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFil
terC
hain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVal
ve.j
ava:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.
invo
keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextVal
ve.j
ava:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.
invo
keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:24
17)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.jav
a:18
0) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.
invo
keNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherV
alve
.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.
invo
keNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.jav
a:17
2) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.
invo
keNext(StandardPipeline.java:641) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:57
7)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.
invo
keNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve
.jav
a:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.
invo
keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.
java
:1040) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java
:115
1) at java.lang.Thread.run(Thread.java:536)
root cause
java.lang.OutOfMemoryError
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
