Am having problems using the ‘disconnect clients’ option in Servoy Server Admin. I go through the disconnect sequence and nothing happens–whether I try to disconnect one client or many, all clients are still on the clients list when I refresh. Possibly related: There shouldn’t be so many active clients, anyway. Looks like they are not auto-disconnecting when they close their client sessions. Also possibly related: Due to the above, they have exceeded their license count.
Jerry, which version do you use? What platform do you use?
Servery 2.1
Win 2k3 for Server
Mix of OS X and Win 2K client workstations
Hmm, that’s strange. The reason I asked this was that my client had this issue working with 1.2.
2.0 and 2.1 didn’t show me this issue. Sorry, can’t guide you here
what happens if you just wait for a few minutes after you fires a disconnect to all of them?
We have tweaked/fixed this behaviour of haning clients a bit more in 2.1.1 which is just around the corner.
jcompagner:
what happens if you just wait for a few minutes after you fires a disconnect to all of them?We have tweaked/fixed this behaviour of haning clients a bit more in 2.1.1 which is just around the corner.
I add a recent experience: I had to restart a server because a customer run out of licenses even if it has only 2 concurrent clients with 5 licenses available.
I think the problem is that, if a client goes to sleep, Servoy correctly doesn’t close it; but if the client is a laptop and to user takes it away while it’s sleeping and then, at home, closes Servoy client, Servoy server has still the client active, even if the computer is not connected anymore.
In this case, you’ll probably not be able to close this client from administration window unless you restart the server.
no these cases are (or should be) handled now, Please let me know if this is fixed when you start using 2.1.1.
jcompagner:
no these cases are (or should be) handled now, Please let me know if this is fixed when you start using 2.1.1.
I certainly will 
In response to…
jcompagner:
what happens if you just wait for a few minutes after you fires a disconnect to all of them?We have tweaked/fixed this behaviour of haning clients a bit more in 2.1.1 which is just around the corner.
Tried waiting. Still no disconnect. And in regard to 2.1.1, I have the new j2db.jar and j2dbdev.jar from 2.1.1 as a result of the ‘Cannot Load Records’ problem and resolution. Have installed those and behavior is the same. Should I see the improved 2.1.1 behavior with just those two jars?
we are still very busy on that field currently..
we hope that by tommorrow we have squashed all of the hanging client bugs..