[erlang-questions] SSL connection is closed unexpectedly

Alex Shneyderman a.shneyderman@REDACTED
Thu Jan 17 14:31:58 CET 2013

On Thu, Jan 17, 2013 at 3:26 AM, Ingela Andin <ingela.andin@REDACTED> wrote:
> Hi!
> 2013/1/15 Alex Shneyderman <a.shneyderman@REDACTED>:
>> Hello, everybody!
>> I had a need to STARTTLS-enable tsung's jabber client. I use ssl
>> engine that comes with R15B02. Basically, code takes an existing
>> socket (tsung client - FSM owns that socket) and does an upgrade to
>> TLS at an appropriate moment in time. Like so:
>>       {ok,SslSocket} = ssl:connect(Socket, [{verify,
>> verify_none},{reuse_sessions,false}]),
>>       ssl:controlling_process(SslSocket,ClientFSMPid),
>>       ssl:setopts(SslSocket,[{active, once}]),
>> If I spawn some number of clients (the number varies but anything
>> beyond 200 seems to cause the problem) - connections get dropped and I
>> believe it is the client side that drops the connections (since this
>> behavior is not observed without TLS in the picture). So the
>> questions:
>> 1. Is this a known default behavior? If so how do I make it go away,
>> i.e. some of the tests we are running need 2000 clients and plain
>> (non-tls).
> No it is not.  What server are you running against? Servers may allow different
> number of concurrent connections for TLS and non TLS.

this is ejabberd (2.1.11). I do not think there is
any difference on maximum of connections between
TLS and non-TLS on this server.


More information about the erlang-questions mailing list