[
https://issues.apache.org/jira/browse/COCOON-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581095#action_12581095
]
Grzegorz Kossakowski commented on COCOON-2179:
----------------------------------------------
First observations: it looks like it's problem with recycling poolable
components (AbstractProcessingPipeline in this case). I constantly see
something like that in logs:
[ERROR] PoolableFactoryBean - Exception while putting component '[EMAIL
PROTECTED]' back into the pool. <java.lang.IllegalStateException: No
thread-bound request found: Are you referring to request attributes outside of
an actual web request? If you are actually operating within a web request and
still receive this message,your code is probably running outside of
DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener
or RequestContextFilter to expose the current
request.>java.lang.IllegalStateException: No thread-bound request found: Are
you referring to request attributes outside of an actual web request? If you
are actually operating within a web request and still receive this message,your
code is probably running outside of DispatcherServlet/DispatcherPortlet: In
this case, use RequestContextListener or RequestContextFilter to expose the
current request.
at
org.springframework.web.context.request.RequestContextHolder.currentRequestAttributes(RequestContextHolder.java:102)
at
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:61)
at $Proxy11.putBackIntoAvalonPool(Unknown Source)
at
org.apache.cocoon.core.container.spring.avalon.AvalonServiceManager.release(AvalonServiceManager.java:73)
at
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.recycle(AbstractProcessingPipeline.java:686)
at
org.apache.cocoon.components.pipeline.impl.BaseCachingProcessingPipeline.recycle(BaseCachingProcessingPipeline.java:74)
at
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.recycle(AbstractCachingProcessingPipeline.java:1017)
at
org.apache.cocoon.core.container.spring.avalon.PoolableFactoryBean.enteringPool(PoolableFactoryBean.java:259)
at
org.apache.cocoon.core.container.spring.avalon.PoolableFactoryBean.putIntoPool(PoolableFactoryBean.java:229)
at
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.run(PoolableProxyHandler.java:84)
at
org.springframework.web.context.request.AbstractRequestAttributes.executeRequestDestructionCallbacks(AbstractRequestAttributes.java:76)
[...]
I'm still not sure where is the real cause of this problem in Spring logic or
in Avalon Bridge or in RCL.
> Exception generator doesn't work properly
> -----------------------------------------
>
> Key: COCOON-2179
> URL: https://issues.apache.org/jira/browse/COCOON-2179
> Project: Cocoon
> Issue Type: Bug
> Components: * Cocoon Core
> Affects Versions: 2.2-dev (Current SVN)
> Reporter: Reinhard Poetz
> Assignee: Grzegorz Kossakowski
> Priority: Blocker
>
> I run across some obscure behaviour, when I use the exception generator: The
> problem is that it only works every second request.
> When it fails, following exception is thrown:
> Caused by: org.apache.cocoon.ProcessingException: Generator already set.
> Cannot set genera
> tor 'exception'
> at <map:generate type="exception"> -
> file:///F:/os/cocoon/trunk/blocks/cocoon-it/.
> /src/main/resources/COB-INF/sitemap.xmap:211:43
> at
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setGenerator(A
> bstractProcessingPipeline.java:205)
> I don't remember that I have seen this with RC2.
> I added a sample to cocoon-it and a test case to cocoon-webapp
> (org.apache.cocoon.it.sitemap.ErrorHandlingTest).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
