Managing PiSA cubes sessions

If the client on the local computer doesn’t respond, it may be necessary to close the current instance. The session is not closed automatically on the server. It may occur that sessions are registered that are currently not running and prevent logging in again. A new session is registered on the server for every login from the client, which may cause an overflow.

You should only stop a session as a system administrator if there is no other possibility, e.g., with network errors.

If you stop a session, the server tries to send a message to the affected user, so that they can log off properly. It cannot be guaranteed, however, that this message reaches the client. The operating system may have removed the socket already before the client tries to receive data again. In such a case, the client announces a socket exception and shuts down properly as well.

It is not possible to stop your own session via one of the server monitors.

To terminate corrupt sessions, proceed as follows:

1. Open the PiSA cubes Monitor via the Administrator Tool box.
2. Switch to the Session tab and mark the sessions that were reported as corrupt.
3. Select Stop session from the function bar.
4. Ask the respective user to log on once more.

In normal operation, the JS code in the browser sends so-called "alive" pings that ensure that a "ses­sion timeout" does not occur even if the user fails to act for a longer period of time. However, if the net­work connection is interrupted (e.g. the notebook has gone into suspend mode, VPN is broken, etc.), then these "alive" pings cannot arrive, and at some point the web server (tomcat) clears the session.

There now is the "Sessions Alive Timeout" which is configurable in the admin view of the CRM web client setup (... /pisasales/pisaadmin). It defines how long the web server (tomcat) waits until it assumes that an unresponsive session is gone. The default is 5 minutes.