[erlang-questions] infrequent socket_closed_remotely errors with httpc

Magnus Mueller <>
Wed Feb 26 08:46:45 CET 2014

Switching to HTTP/1.0 seems to work around our issue as well. This is not really satisfying, but should work for our use case.


Von: Shayan Pooya [mailto:] 
Gesendet: Freitag, 21. Februar 2014 06:34
An: Magnus Mueller
Cc: ; Johannes Weißl; Sebastian Egner
Betreff: Re: [erlang-questions] infrequent socket_closed_remotely errors with httpc

On Thu, Feb 20, 2014 at 8:31 AM, Magnus Mueller <> wrote:

We are struggling with a hard-to-reproduce problem with httpc were we sometimes encounter `{error,socket_closed_remotely}` when querying our simple webserver. Sometimes this happens with yaws as well.

The error happens very infrequently and is thus hard to reproduce. Both the webserver and httpc run in the same VM (which might be the cause of the problem). Interestingly, the problem is more likely to occur if the system is under cpu-heavy load, e.g. when using stress[1]:

    stress --cpu 6

Did anybody of you encounter similar problems? We are running out of ideas and I could not yet come up with a small example to reproduce the issue.


[1] https://web.archive.org/web/20130520190152/http://weather.ou.edu/~apw/projects/stress/ , the original website seems to be down.
erlang-questions mailing list


There was a discussion about this last week (http://erlang.org/pipermail/erlang-questions/2014-February/077370.html).
We had a somehow similar issue in Disco, and we worked around it by switching back to HTTP/1.0.

More information about the erlang-questions mailing list