When an application is disabled, the session manager will start its shutdown sequence by terminating all existing sessions. It will then shut itself down and exit. Since the termination notification to existing clients is done asynchronously, it is possible that the session manager may have shutdown and exited before all notifications have been sent out to connected clients.
If the client receives the termination notification before the session manager exits, it will receive an exception similar to the following:
Domain <Application>: Cannot operate on session. The session no longer exists because the application is disabled.
If the client does not receive the termination notification before the session manager exits, it will receive an exception similar to the following:
Domain <Application>: Connection to the system broken. It is likely that there is either a network problem or the SOA Middleware may be unavailable at this time.