forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Williams (JIRA)" <>
Subject [jira] Commented: (FOR-591) MaxMemory needs increasing for large document sets: Memory Leak with XMLFileModule
Date Fri, 28 Aug 2009 00:48:59 GMT


Tim Williams commented on FOR-591:

Can anyone confirm that this isn't a "drop-in" replacement?  A simple switch from XMLFileModule
to XPathXMLFileModule leads me to an error like:

"Caused by: org.apache.avalon.framework.configuration.ConfigurationException: No attribute
named "src" is associated with the configuration element "file" at <generated>file:/Users/twilliams/Development/forrest/main/webapp/WEB-INF/cocoon.xconf:248:56"

My initial hunch is that the original version allowed lazy loading of the source the new XPathXMLFileModule
does not but before I looked into it too much I wanted to see if someone experiences the same?

fwiw, tracking just this little problem down in the unnavigable mess that has become the cocoon
source leads me wanting to pursue the oft proposed forrest2...

> MaxMemory needs increasing for large document sets: Memory Leak with XMLFileModule
> ----------------------------------------------------------------------------------
>                 Key: FOR-591
>                 URL:
>             Project: Forrest
>          Issue Type: Bug
>          Components: Core operations
>    Affects Versions: 0.7, 0.8
>            Reporter: Ross Gardler
>            Priority: Blocker
>             Fix For: 0.9-dev
> Since the docs restructuring for the 0.7 release it has become necessary to increase
the maxmemory to be able to build the Forrest site. We gained three copies of the documents
so suddenly have a large document set to trigger memory leakage issues.
> Possibly COCOON-1574 "Memory Leak with XMLFileModule".
> Does someone have the tools to run some diagnostics?
> (NB maxmemory has been increased in our site-author/, if we resolve
this issue it should be reduced again)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message