RE: Any clue on this, please? Uploading large files - out of memory
Or, configuration. Consider what I ran into the last few weeks. We were doing very high load testing of Tomcat and getting the dreaded OutOfMemory error simply hitting the Tomcat examples. I immediately thought this to be bug as well. Well, after using OptimizeIt on the code, I found out that the culprit is that we were creating so many sessions that we used up all of the memory before we hit the session timeout. This is a tuning problem, not a bug. I could 1) Throw more memory at Tomcat (we had -Xmx256m) 2) Decrease the session timeout. The default is good in most cases of not-so-extreme traffic 3) Ponder on whether load testing 500-600 req/s, with each request being a completely new session is a valid test scenario. (Sometime it is: Think getting slash-dotted) I also think that a lot of the more bizarre OOM errors being reported on the user list currently, when reloading contexts for instance, have to do with the newer GC model of new/old/permanent generation divisions - the permanent generation is filling even though old and new have room to spare. This is also tuning. (Well, the user did say that Sun is doing a "fix" for that, so I guess it could be either) That all said, OptimizeIt is well worth the money spent. It vastly decreased the amount of time spent tracking down my OOM error. (After 3 or so days of staring at heap dumps, we just got OptimizeIt, and found the problem almost immediately). >On Wed, 3 Dec 2003, Adam Fisk wrote: > >> I've heard mention on this list many times of these OutOfMemoryErrors >> not being bugs. I work on a Java app that experiences very high network >> traffic load, however, and it's been my experience that >> OutOfMemoryErrors are, in fact, always bugs regardless of how tempting >> it is to chalk it up to something else. >> >> 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 Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Any clue on this, please? Uploading large files - out of memory
I unfortunately don't have the time to step through each and every thread where these errors are occuring, although I wish I did. The question is, has someone done this? It's about the most tedious coding process I know of, so it just wouldn't surprise me if no one's actually done it. Do you know what threads these errors occur in? If so, do you know when they occur? Can you reproduce them? Clearly there are legitimate OOMEs, there just much rarer than the illegitimate ones. It's the legitimacy or illegitimacy that's tough to determine. I'm sure this process has happened, but then again, maybe not. -Adam Shapira, Yoav wrote: Howdy, I would throw out one more piece of advice: consider jakarta commons fileupload component. It is well-designed with respect to handling large files. As to the "OutOfMemoryErrors are, in fact, always bugs" claim -- well, that's the most amusing thing I've heard today ;) If they are bugs, find the buggy code. Yoav Shapira Millennium ChemInformatics -Original Message- From: Fabrizio Nesti [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 2:01 PM To: Tomcat Developers List Subject: Re: Any clue on this, please? Uploading large files - out of memory Indeed I am not 100% sure of the real cause of the OOME below. However, as far as my request is concerned, it seems that the upload component that we use (Echopoint's one, quite cool) _could_ (and should) have used an InputStream. So this is enough for me to go bother them and no longer the tomcat-dev :). I was thinking that tomcat was the critical point, so I wrote here just to be sure. In case you need further testing please let me know, for the rest it's up to you tomcat developers... and... thanks for your good work. cheers, Fabrizio On Wed, 3 Dec 2003, Adam Fisk wrote: I've heard mention on this list many times of these OutOfMemoryErrors not being bugs. I work on a Java app that experiences very high network traffic load, however, and it's been my experience that OutOfMemoryErrors are, in fact, always bugs regardless of how tempting it is to chalk it up to something else. 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(Appli c atio nFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFi l terC hain.java:193) at org.apac
RE: Any clue on this, please? Uploading large files - out of memory
Howdy, I would throw out one more piece of advice: consider jakarta commons fileupload component. It is well-designed with respect to handling large files. As to the "OutOfMemoryErrors are, in fact, always bugs" claim -- well, that's the most amusing thing I've heard today ;) If they are bugs, find the buggy code. Yoav Shapira Millennium ChemInformatics >-Original Message- >From: Fabrizio Nesti [mailto:[EMAIL PROTECTED] >Sent: Wednesday, December 03, 2003 2:01 PM >To: Tomcat Developers List >Subject: Re: Any clue on this, please? Uploading large files - out of >memory > >Indeed I am not 100% sure of the real cause of the OOME below. >However, as far as my request is concerned, it seems that the upload >component that we use (Echopoint's one, quite cool) _could_ (and should) >have used an InputStream. > >So this is enough for me to go bother them and no longer the tomcat-dev :). >I was thinking that tomcat was the critical point, so I wrote here just to >be sure. > >In case you need further testing please let me know, for the rest it's up >to >you tomcat developers... and... thanks for your good work. > >cheers, >Fabrizio > > >On Wed, 3 Dec 2003, Adam Fisk wrote: > >> I've heard mention on this list many times of these OutOfMemoryErrors >> not being bugs. I work on a Java app that experiences very high network >> traffic load, however, and it's been my experience that >> OutOfMemoryErrors are, in fact, always bugs regardless of how tempting >> it is to chalk it up to something else. >> >> 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
Re: Any clue on this, please? Uploading large files - out of memory
Indeed I am not 100% sure of the real cause of the OOME below. However, as far as my request is concerned, it seems that the upload component that we use (Echopoint's one, quite cool) _could_ (and should) have used an InputStream. So this is enough for me to go bother them and no longer the tomcat-dev :). I was thinking that tomcat was the critical point, so I wrote here just to be sure. In case you need further testing please let me know, for the rest it's up to you tomcat developers... and... thanks for your good work. cheers, Fabrizio On Wed, 3 Dec 2003, Adam Fisk wrote: > I've heard mention on this list many times of these OutOfMemoryErrors > not being bugs. I work on a Java app that experiences very high network > traffic load, however, and it's been my experience that > OutOfMemoryErrors are, in fact, always bugs regardless of how tempting > it is to chalk it up to something else. > > 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 > > > >
Re: Any clue on this, please? Uploading large files - out of memory
I've heard mention on this list many times of these OutOfMemoryErrors not being bugs. I work on a Java app that experiences very high network traffic load, however, and it's been my experience that OutOfMemoryErrors are, in fact, always bugs regardless of how tempting it is to chalk it up to something else. 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.StandardPipel
Re: Any clue on this, please? Uploading large files - out of memory
Please followup to tomcat user. 1) Make sure that the app is using ServletRequest.getInputStream() 2) See the spec: 'SRV.4.1.1 When Parameters Are Available' -Tim Fabrizio Nesti wrote: 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? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Any clue on this, please? Uploading large files - out of memory
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 > > > > >---
