Re: Cocoon protocol memory leak

> 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.