We have an app with a single long lived session.

When we want to do something, we

- get the session instance
- check if the session isConnected and isOpen
- beginTransaction
- do stuff
- commit or rollback

Intermittently ( and very infrequently ) the isConnected check fails.

Why would a long running session suddenly become disconnected?

Is it actually appropriate to check that the session is connected before we start a transaction?

TIA
Perryn

If you ignore the false isConnected() does the session
reconnect when you actually try to do something?

I'm no expert, but I was under the impression that the underlying
DB connection could get closed (timeout, for instance) and the
session manager will just reconnect next time you ask for
something.