[erlang-questions] Inets concurrent limit
Martin Logan
martin.logan@REDACTED
Tue Oct 21 04:25:15 CEST 2008
That is one of the problems I did run into. Was hitting ulimits as well.
Both problems are fixed now and the proxy flies :) Thanks for the response.
Cheers,
Martin
On 10/17/08 5:53 PM, "Edwin Fine" <erlang-questions_efine@REDACTED> wrote:
> Martin,
>
> I wonder if you are running into the TCP/IP ephemeral port starvation problem?
>
> There's more information about this (and how to reduce problems due to it) in
> a post I wrote a little while ago:
>
> http://www.erlang.org/pipermail/erlang-questions/2008-September/038154.html
>
> Hope this helps.
>
> Regards,
> Edwin
>
> 2008/10/17 Logan, Martin <Martin.Logan@REDACTED>
>> Does inets have a limit on the number of concurrent requests it can handle
>> both inbound and outbound. On the inbound side when I really ramp up load I
>> see 503 responses quite a bit, I am also seeing sporadic 500's. On the
>> outbound side (this thing I am testing is an http proxy) I am seeing issues
>> with addrinuse, which looks to be an OS issue so I am investigating that as a
>> separate issue. Anyhow, any inets info you can provide would be helpful.
>> Basically I am looking to be able to drive as much traffic though this thing
>> as I can.
>>
>>
>>
>> Cheers,
>>
>> Martin
>> If you are not the intended recipient of this e-mail message, please notify
>> the sender
>> and delete all copies immediately. The sender believes this message and any
>> attachments
>> were sent free of any virus, worm, Trojan horse, and other forms of malicious
>> code.
>> This message and its attachments could have been infected during
>> transmission. The
>> recipient opens any attachments at the recipient's own risk, and in so doing,
>> the
>> recipient accepts full responsibility for such actions and agrees to take
>> protective
>> and remedial action relating to any malicious code. Travelport is not liable
>> for any
>> loss or damage arising from this message or its attachments.
>>
>>
>>
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://www.erlang.org/mailman/listinfo/erlang-questions
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20081020/18f337e1/attachment.htm>
More information about the erlang-questions
mailing list