Use SSL in multiple connections

[Souheila Hechaichi]

With my actual configuration, an SSL client established more connections with 
the SSL server. Each process (server or client) creates only one thread for Its 
sockets,  I observe a strange behavior. Some server sockets remain blocked on 
the call of SSL_write even if they are in mode non-blocking. Side client some 
sockets loop indefinitely on the call of SSL_read that return 
SSL_ERROR_WANT_READ.
Hence my question:
Is It mandatory to create a thread by connection, or can only one thread be 
used by all the connections?

Best regards;

SSL server send packet FIN than data user.More the client answer with RST packet

[Souheila Hechaichi]

After establishing a secure connection between my SSL server and SSL client 
with OpenSSL library installed on separate Linux hosts, the SSL server send the 
packet FIN than the user data. The use of ssldump command indicates the 
presence of the following traces:
TCP: dc01dshared1p(2524) -> dc01dadaperf1p.atempo.dev(50814) Seq 2822753961.(0) 
ACK 136721005 FIN
1057311.4840 (57311.0739)  S>C  TCP FIN
They mean SSL server send end of send data (FIN packet).
On the packet FIN, the client sends RST packet
TCP: dc01dadaperf1p.atempo.dev(50814) -> dc01dshared1p(2524) Seq 136721005.(0) 
ACK 2822753962 RST
1057311.6295 (0.1454)  C>S  TCP RST

Can you help me to known why the SSL server send FIN then data user and to 
resolve the problem?
Best regards;