Re: Frustrating "java.lang.OutOfMemoryError" problems

WHIRLYCOTT Wed, 02 Feb 2005 04:25:08 -0800

What you're seeing in the windows task manager is misleading. If you have -Xmx256M, it would not be unusual for you to see ~350M being used in task manager. The extra ~100M (sometimes less, sometimes more) represents the memory used by the jvm which itself is then using 256M. If you want to monitor this, just write a little servlet that logs memory usage as reported by java.lang.Runtime.(max||free||total)Memory().

In tracking issues like this in the past, I've used Borland Optimizeit, because you can connect it remotely to the jvm and monitor object creation and destruction, etc. It's pricey, but there's a 30 day trial... and if you can't fix the problem in 30 days, you may not have a job anyway, so it's usually enough time ;)

phil.

Derek Hohls wrote:

Running: Cocoon 2.1.5; Tomcat/4.1.29; Java 1.4.2; WindowsXP

I keep bumping my head into memory problems with *some* Cocoon operations. See the log snippet below - I am trying to serialize a SVG file to JPEG -> the process works fine when the file sizes are from 1-250k. As files gets larger (300-500k), I eventually get the dreaded java.lang.OutOfMemoryError message in the Tomcat server log. In fact, in some cases Cocoon *can* process the larger file, but as soon as I hit 'refresh' the memory overflows.

If I use the Windows task Manager; it seems that Tomcat is not using more than about 132MB... the settings for Java *should* allow it to use up to 256MB... ie. CATALINA_OPTS is set to: -Xms64m -Xmx256m -Dfile.encoding=ISO-8859-1 -DproxySet=true -DproxyPort=3128 When I run other processes through Cocoon e.g. some of the samples then the memory usage can hit about 147MB.

Any assistance with this is gratefully appreciated.

Thanks
Derek

PS I am not sure this is related, but I get similar problems when
working with the directory generator
  <map:generate src="dir" type="directory" include="*.xml"/>
after some random number of refreshes, this operation, too, causes a
memory problem.


2005-02-01 18:27:52 StandardWrapperValve[Cocoon]: Servlet.service() for
servlet Cocoon threw exception
javax.servlet.ServletException: Servlet execution threw an exception
        at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
        at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
        at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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(StandardContextValve.java:191)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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:2417)
        at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
        at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
        at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.java:174)
        at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:193)
        at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:781)
        at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:549)
        at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
        at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666)
        at java.lang.Thread.run(Thread.java:534)
----- Root Cause -----
java.lang.OutOfMemoryError

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
                                  Whirlycott
                                  Philip Jacob
                                  [EMAIL PROTECTED]
                                  http://www.whirlycott.com/phil/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Frustrating "java.lang.OutOfMemoryError" problems

Reply via email to