Re: kill a socket

Am Dienstag, den 11.03.2008, 07:57 +0100 schrieb Peter Halacsy:
> Peter Halacsy wrote:
> > Gerd Stolpmann wrote:
> > 
> >> No. If the header isn't set you have to count the bytes.
> >>
> > 
> > 
> > yes, I have to count. Now I get the next error. It's interesting that 
> > the full buffer is'nt deleted after the failure: when I rerun the 
> > pipeline got the same failure
> > 
> > Failure: Netbuffer: string too largeFailure("Netbuffer: string too 
> > large") - Continuing with next element...
> > 
> > 
> 
> Gerd,
> 
> I've created a new mime_body that raises an exception if the body is too 
> large. Everything works if i raise a custom exception. It's very strange 
> that after a Failure the pipeline doesn't  clean its own state up: after 
> rerunning I got the same exception.
> 
> Maybe the pipeline doesn't closes the connection that raised the Failure.

Do you have some code that reproduces the error? 

Gerd
-- 
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany 
[email protected]          http://www.gerd-stolpmann.de
Phone: +49-6151-153855                  Fax: +49-6151-997714
------------------------------------------------------------



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace