Grzegorz Kossakowski schrieb:
> That's weird. Any clue about that?

The problem is a missing HTTP status code when the response is committed. 
This happens due to Reinhard's change for the dynamic setting of the status 
code (see below), that I just got when updating to your servlet changes. 
When putting these lines back into the code, the exception disappears.

 > Author: reinhard
 > Date: Thu Apr 19 06:28:04 2007
 > New Revision: 530409
 >
 > URL: http://svn.apache.org/viewvc?view=rev&rev=530409
 > Log:
 > we can't set the response status here as it overrides the status-code 
value which was set by the serializer
 >
 > Modified:
 > 
cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-impl/src/main/java/org/apache/cocoon/components/pipeline/AbstractProcessingPipeline.java
 > @@ -548,8 +546,6 @@
 >              handleException(e);
 >          }
 >
 > -        //Request has been succesfully processed, set approporiate 
status code
 > -        environment.setStatus(HttpServletResponse.SC_OK);
 >          return true;
 >      }
 >
 > @@ -661,8 +657,6 @@
 >              handleException(e);
 >          }
 >
 > -        //Request has been succesfully processed, set approporiate 
status code
 > -        environment.setStatus(HttpServletResponse.SC_OK);
 >          return true;
 >      }

Alex

-- 
Alexander Klimetschek
http://www.mindquarry.com