If this occurs as often as written by Alfred ("I get an NPE in ECS.release always for the first request after touching the sub-
sitemap"), we maybe have the blocking issue for the release.
Joerg
Unico Hommes wrote:
Whenever reloading the portal-fw samples-fw sitemap. I'm seeing the following NullPointerException:
java.lang.NullPointerException at org.apache.cocoon.components.ExtendedComponentSelector.release(ExtendedC omponentSelector.java:317) at org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.dispose(Se lectNode.java:169) at org.apache.cocoon.components.treeprocessor.TreeProcessor.disposeTree(Tre eProcessor.java:472) at org.apache.cocoon.components.treeprocessor.TreeProcessor.setupRootNode(T reeProcessor.java:422) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro cessor.java:319) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro cessor.java:307) at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(Moun tNode.java:133) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:84) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.i nvoke(PreparableMatchNode.java:164) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P ipelineNode.java:164) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke( PipelinesNode.java:161) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro cessor.java:325) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro cessor.java:307) at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(Moun tNode.java:133) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:84) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.i nvoke(PreparableMatchNode.java:164) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(P ipelineNode.java:164) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode. invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke( PipelinesNode.java:161) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro cessor.java:325) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreePro cessor.java:307) at org.apache.cocoon.Cocoon.process(Cocoon.java:621)
Would an additional null check suffice or is this a symptom of a different problem?
