On 13.05.2009, at 17:40, Will Sheppard wrote:
After we replaced all the ‘cocoon:’ protocol calls with 'http://localhost/path/to/cocoon'
, the memory leak disappeared. No matter how many times or how fast
the pipeline was hit, memory usage would always come down just
before it reached 100Mb. It would stabilise at around 40-50Mb after
garbage collection. We only made that one change to the sitemap.
But we'd really like to use the cocoon: protocol, so that the error
stack is followed properly upon errors (among other reasons). When
using the 'localhost' method, the stack trace stops at the last URL
accessed.
Has anyone encountered an issue like this memory leak, or knows of a
solution?
We are using Cocoon 2.2 under JBoss 4.2.2 on 64-bit Linux.
I also encountered the issue and fortunately after many days browsing
through jhat heap dumps [1] and debugging Cocoon I found a solution: https://issues.apache.org/jira/browse/COCOON-2259
Please let us know if it fixes your memory leak.
Have fun, Alex
[1] http://java.sun.com/javase/6/docs/technotes/tools/share/jhat.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
