This morning one of our customer experienced a network failure for several of its workstations. I was surprised by the fact that connexions (and associated processes) were still alive for several minutes on the database server. Unfortunately, ou client application is not very well designed and open several db connexions simultaneously. This caused the total number of connexions to double on the server, while memory pressure was already high.
Is it by desgin ? Is there a server parameter to force the associated process to close if the client connexion is gone ? This behavior could be easily reproduced but unplugging the network cable on a client workstation while connected to the server.
I'm not sure what finally triggered those connexions to close automatically but it take too much time.