Re: kill a socket
Peter Halacsy <[email protected]> Tue, 11 Mar 2008 07:57:43 +0100
| Newsgroups | gmane.comp.lang.ocaml.lib.net.devel |
|---|---|
| Message-ID | <[email protected]> |
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.
peter
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/