jacker wrote on Jan 5^th, 2017 at 5:24pm:


It is self correcting in regards to network communication in the same way that 2.5 was, and has even more network self correcting(It can reconnect after a drop in network communication)  You'll see the client connection count decrease after a short amount of time(<2 minutes) after killing a client process.

A few questions that may narrow down what was happening:
Was the Sesame process on the Server computer using CPU and Memory at the time that no body could connect?
Was the Sesame Server processing commands? This can be seen on the Server window.

-Ray

The clients that are currently connected, are they still able to function?

What are the currently connected clients doing when this happens? If they are running a large routine, does it continue to run?

Does the commands processed(the first number in that section) change when a new client attempts to connect? If so by how many?

On the Server computer, when this happens if you bring up a command prompt and run a NetStat command(Netstat /a /b /p tcp will give you all the TCP ports open and what program opened them) are both communication ports(20,000 and 20,001 by default) open on the Sesame Server? Are there two communication ports open to each Sesame client as well?

In the disconnected client list, does one computer show up over and over again? That indicates a communication issue with that particular client.

-Ray

Just did an Emergency Shutdown since I couldn't connect either...unlocked all the apps and dbs.

One office is still having issues, getting kicked off and having a hard time getting connected. They are the ones showing up in red:

Stop Server doesn't seem to work...

It happens often on Monday mornings, especially if clients forget to exit Sesame over the weekend...the apps themselves are very simple, just adding or updating records manually, no batch processing or fancy subroutines.

The server is a commercial cloud server with the Sesame ports whitelisted on the firewall, so it should be rock solid. These issues are all intermittent, Sesame runs fine most of the time.

One definite issue is when a user can't connect and launches Sesame over and over and does not realize that multiple processes are running in the background. Once the license limit is reached, corruption occurs and EVERYONE will no longer be able to use Sesame or even connect. Even if everyone disconnects, at this point Sesame is dead in the water. I have to manually shut down and restart the server, and unlock all the databases in order for anyone to proceed normally. I have to do this about 3 or 4 times a week.