We're using the borland socket server trough 14 ports, linked to an AS/400 server. During weekends, when we have +500 logins a day, from time to time connections get lost.
They keep appearing in the overview of the open connections, but these connections are still open. Even though the client isn't in use anymore. This means we need to restart the server (Because the socket server crashes), remove all lost connections. We need to close the refering server an restart it. All our users need to CTRL-ALT-DEL there client, and login again, and again we need to remove those lost connections.
About these connections; if i ask a netstat on our server, these connections still seem to be open, when a connection is lost. So i don't know if windows doesn't close the connection correctly, or it is borland socket server which doesn't close them correctly
They keep appearing in the overview of the open connections, but these connections are still open. Even though the client isn't in use anymore. This means we need to restart the server (Because the socket server crashes), remove all lost connections. We need to close the refering server an restart it. All our users need to CTRL-ALT-DEL there client, and login again, and again we need to remove those lost connections.
About these connections; if i ask a netstat on our server, these connections still seem to be open, when a connection is lost. So i don't know if windows doesn't close the connection correctly, or it is borland socket server which doesn't close them correctly