stunnel socket bug shutdown

[Dave]

The stunnel server runs out of socket resources. A netstat -a shows
that there are a number of sockets in CLOSE state. Apparently, stunnel
is not doing a shutdown( ) followed by a close( ) on these sockets.

The stunnel server is run as:
stunnel -f -d 30003 -r localhost:30004

The stunnel client is also running

The problem occurs in a scenario where the application daemon which
typically listens on 30004 is not actually running. Each time an
application client connects to the stunnel client, the stunnel client
succesfully negotiates with the stunnel server. The stunnel server
attempts to communicate with the application server, but fails to the
socket is left in a state where it does not shut completely down.