Jean-Baptiste Quenot schrieb: > * Max Pfingsthorn: >> org.apache.cocoon.ProcessingException: Unable to remove component from >> automatic release: no environment available. >> at >> org.apache.cocoon.components.CocoonComponentManager.removeFromAutomaticRelease(CocoonComponentManager.java:489) >> at >> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.release(AbstractProcessingPipeline.java:184) >> at >> org.apache.cocoon.components.source.impl.SitemapSource.reset(SitemapSource.java:433) >> at >> org.apache.cocoon.components.source.impl.SitemapSource.recycle(SitemapSource.java:460) >> at >> org.apache.cocoon.components.source.impl.SitemapSourceFactory.release(SitemapSourceFactory.java:78) >> at >> org.apache.excalibur.source.impl.SourceResolverImpl.release(SourceResolverImpl.java:269) > > Same here. Happens when using « cocoon: » which is implemented by > SitemapSource. This object is not properly released/recycled/reset > upon concurrent requests. This does not happen on my development > server, but happens on a production server. This is harmless but > annoying. You may just disable the error reporting if you wish. It would be great if you or Max could come up with some test case so we can reproduce the problem and then try to fix it.
Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
