[jira] Commented: (COCOON-2179) Exception generator doesn't work properly
[ https://issues.apache.org/jira/browse/COCOON-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12581072#action_12581072 ] Grzegorz Kossakowski commented on COCOON-2179: -- Reinhard, as you are busy with preparing the release I decided to give this one a shoot. :-) 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 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.
[jira] Commented: (COCOON-2179) Exception generator doesn't work properly
[ https://issues.apache.org/jira/browse/COCOON-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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.
[jira] Commented: (COCOON-2179) Exception generator doesn't work properly
[ https://issues.apache.org/jira/browse/COCOON-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580682#action_12580682 ] Reinhard Poetz commented on COCOON-2179: Looking at the currently failing integration tests I think that we really have a problem with the environment cleanup (as being guessed by Grek): --- Test set: org.apache.cocoon.it.servletservice.SubSitemaps --- Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.51 sec FAILURE! testSimplePipelineFromSubSitemap(org.apache.cocoon.it.servletservice.SubSitemaps) Time elapsed: 0.45 sec ERROR! com.gargoylesoftware.htmlunit.FailingHttpStatusCodeException: 500 Generator already set. Cannot set generator 'file' at map:generate - /blocks/cocoon-servlet-service-sample/test1/sub/sitemap.xmap:26:39 at map:match - /blocks/cocoon-servlet-service-sample/test1/sub/sitemap.xmap:25:33 at map:mount - /blocks/cocoon-servlet-service-sample/test1/sitemap.xmap:83:49 at map:match - /blocks/cocoon-servlet-service-sample/test1/sitemap.xmap:82:35 for http://localhost:/cocoon-servlet-service-sample1/sub/test at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:346) This only happens when I run the integrationt tests but not when I access the URL directly with a browser :-/ 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 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.