Sometimes when disconnecting all clients not all clients are disconnected. I have to actually shut down the FMS process in admin panel to get the DB to start Closing. The closing process is very slow even when all the clients are in fact disconnected but showing a connection. WebDirect disconnect time set to 10 mintues. Waited over 15 minutes for connections to get closed automatically, but it did not happen.
This gets even more interesting:
File closed for over 20 minutes and console still showing 7 connections. ???
Status tab shows 8 connections. Activity tab shows 7. FMS service was stopped 20 minutes ago.
Shutting down the Web Engine cleared all the connections quickly.
Annoying, isn't it?
But keep up this fabulous work - it'll be a huge benefit to us all!
This was using FMS14.0.4 on Windows Server 2012 single machine deployment. This is very repeatable and if no one has any insight I will report it as a bug. There is no reason that I should have to manually shut down the server and/or turn off the Web Engine to disconnect clients.
Must have been a buggy WPE install. I reinstalled and all is working as expected.
Incidentally, I've seen this type of behavior before in 13, but the "ghost" connections were always cleaned up when the max timeout for the session was reached. I never did the level of testing you did and never really attempted to force the connections shut, but they did eventually disappear.