[
https://issues.apache.org/jira/browse/COCOON-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Hartmann reopened COCOON-889:
-------------------------------------
This problem still occurs. It is reproducable in Lenya 1.4-dev revision 527465,
based on Cocoon 2.11-dev revision 527435. When you log in to the default
publication, the exception stack trace is logged to the console.
java.lang.NullPointerException
at
org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:561)
The sourceResolver field is null, i.e. finishingProcessing() has been called
before release().
The problem occurs when a pipeline is called during a CInclude resolving, and
this pipeline calls another one using the cocoon:// protocol.
> NPE in AbstractEnvironment class
> --------------------------------
>
> Key: COCOON-889
> URL: https://issues.apache.org/jira/browse/COCOON-889
> Project: Cocoon
> Issue Type: Bug
> Components: * Cocoon Core
> Affects Versions: 2.1.2
> Environment: Operating System: Linux
> Platform: PC
> Reporter: Ivan Kurmanov
>
> java.lang.NullPointerException
> at
> org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:521)
> at
> org.apache.cocoon.environment.wrapper.MutableEnvironmentFacade.release(MutableEnvironmentFacade.java:332)
> at
> org.apache.cocoon.generation.FileGenerator.recycle(FileGenerator.java:89)
> at
> org.apache.avalon.excalibur.pool.ResourceLimitingPool.put(ResourceLimitingPool.java:438)
> at
> org.apache.avalon.excalibur.component.PoolableComponentHandler.doPut(PoolableComponentHandler.java:245)
> at
> org.apache.avalon.excalibur.component.ComponentHandler.put(ComponentHandler.java:452)
> at
> org.apache.avalon.excalibur.component.ExcaliburComponentSelector.release(ExcaliburComponentSelector.java:336)
> at
> org.apache.cocoon.components.ExtendedComponentSelector.release(ExtendedComponentSelector.java:326)
> at
> org.apache.cocoon.components.ExtendedComponentSelector.release(ExtendedComponentSelector.java:323)
> at
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.recycle(AbstractProcessingPipeline.java:641)
> at
> org.apache.cocoon.components.pipeline.impl.BaseCachingProcessingPipeline.recycle(BaseCachingProcessingPipeline.java:112)
> at
> org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.recycle(AbstractCachingProcessingPipeline.java:961)
> at
> org.apache.avalon.excalibur.pool.ResourceLimitingPool.put(ResourceLimitingPool.java:438)
> at
> org.apache.avalon.excalibur.component.PoolableComponentHandler.doPut(PoolableComponentHandler.java:245)
> at
> org.apache.avalon.excalibur.component.ComponentHandler.put(ComponentHandler.java:452)
> at
> org.apache.avalon.excalibur.component.ExcaliburComponentSelector.release(ExcaliburComponentSelector.java:336)
> at
> org.apache.cocoon.components.ExtendedComponentSelector.release(ExtendedComponentSelector.java:326)
> at
> org.apache.cocoon.components.EnvironmentDescription.release(CocoonComponentManager.java:602)
> at
> org.apache.cocoon.components.CocoonComponentManager.endProcessing(CocoonComponentManager.java:212)
> at org.apache.cocoon.Cocoon.process(Cocoon.java:660)
> at
> org.apache.cocoon.bean.CocoonWrapper.getPage(CocoonWrapper.java:535)
> at
> org.apache.cocoon.bean.CocoonBean.processTarget(CocoonBean.java:521)
> at org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:372)
> at org.apache.cocoon.Main.main(Main.java:388)
> The same exception repeated three times for a single request/file, although it
> is generated through three different calling classes.
> The general picture: I use Forrest, which got me 2.1.2-dev version of Cocoon.
> I
> edited the sitemap.xmap to remove unnecesary things, like PDF generation (FO
> processing) and alike. Didn't change pool-* settings.
> In site.xml I have an item with href='/'. This item is referenced in one of
> the
> pages. This quite well might be a Forrest bug, but maybe Cocoon also need to
> be
> more careful about null pointers in this case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
