Our site uses xsp documents compiled and served by cocoon.  We're
working on a server upgrade to the latest versions of tomcat and
cocoon.  In the upgraded configuration, the server dies with the
following message after a certain fairly large number of distinct
documents have been viewed/compiled.

java.lang.OutOfMemoryError
Jan 6, 2004 10:35:11 AM
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run
SEVERE: Caught exception (java.lang.OutOfMemoryError) executing
[EMAIL PROTECTED], terminating thread

Runtime.getRuntime().freeMemory() indicates that plenty of memory if
free in the JVM (more than 200 MB free!).  No document that's being
viewed is doing any processing at all -- in fact we have it configured
to immediately return at the beginning of the document, so the problem
is not a page that's consuming too much memory, but rather seems to be a
problem with cocoon's XSP caching.

I'm using cocoon 2.1.3 and tomcat 5.0.16.  The problem occurs with both
the sun j2sdk 1.4.0 and j2sdk 1.4.3_03.  This problem does not occur
with visiting jsp files; only the cocoon xsp files.  The problem does
not occur with tomcat 4.0.1 and cocoon 2.0.3.  The problem does not
appear to be stylesheet related since it occurs even when simply viewing
the unstyled raw XML output from the XSP page.

I've tried playing around with the core.store.janitor configuration
without success; don't think that this is the problem though since
plenty of memory is available as I said.

One odd thing: since the upgrade tomcat always prints something like:
Jan 6, 2004 10:56:59 AM org.apache.jk.server.JkCoyoteHandler action
INFO: Response already commited 
Jan 6, 2004 10:56:59 AM org.apache.jk.server.JkCoyoteHandler action
INFO: Response already commited 

each time one of the XSP documents is viewed.  Not sure what's causing
this, since we're not doing anything like setting headers or response
codes in the XSP page, or even if this is related.

Any help you could provide would be very much appreciated.

-Rob Adams
On-Site Manager, Inc.



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

Reply via email to