[erlang-questions] {error,closed} vs. {error,econnreset}

Bekes, Andras G Andras.Bekes@REDACTED
Tue Aug 11 14:43:18 CEST 2015

Hi Rory,

I just tested this new feature in Erlang/OTP R18 and it works fine.

Thank you very much all for implementing it!


-----Original Message-----
From: erlang-questions-bounces@REDACTED [mailto:erlang-questions-bounces@REDACTED] On Behalf Of Rory Byrne
Sent: Wednesday, June 24, 2015 2:48 PM
To: erlang-questions@REDACTED
Subject: Re: [erlang-questions] {error,closed} vs. {error,econnreset}

Hi Andras,

On Tue, May 05, 2015 at 07:44:47AM +0000, Bekes, Andras G wrote:
> Thank you very much for your efforts Rory.
> The ability "to set a socket option that shows all econnreset errors" sounds like the right solution. I am wondering why hiding this detail is the default, but I believe there were good enough reasons to design it that way.
> I accept that your solution will not notice the connection reset event in some corner cases. I think this will not apply in my case: I am sending a small amount of data (<1KB) and wait for the reply.
> I am looking forward to see your patch in the next release of Erlang/OTP!

The fix for this is in the 18.0 release. It should take care of the
corner cases too.

Use the socket option '{show_econnreset, true}' and you'll receive
{error, econnreset} in passive mode or {tcp_error, Socket, econnreset}
in active mode. See the docs [1] for more information.



[1] http://www.erlang.org/doc/man/inet.html#setopts-2
erlang-questions mailing list

More information about the erlang-questions mailing list