Matt- thanks for your suggestions. Unfortunate as our application requires AUTOCOMMIT=FALSE; AUTO_RECONNECT is not an option. Also this would just help for situations when a reconnect succeeds, and still leave stale sessions.
I am aware of cancel_session(). It is documented as "Cancels the currently executing statement of another session." and exactly behaves as such. The session will still exist after using this function. Thanks, Christian Am Montag, 9. September 2019 15:14:19 UTC+2 schrieb Matt Pavlovich: > > Look into setting these combinations: > > 1. On the server: h2.socketConnectTimeout > 2. On the client urls: ;AUTO_RECONNECT=TRUE > > The behavior will be that clients re-connect over and over (harmless, but > not ideal) but you won’t have stale connections or abandoned locks. > > > Also note— there already exists a function to close sessions: > > http://www.h2database.com/html/functions.html#cancel_session > > -Matt > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/85da94da-4f40-4634-8de1-ba1cf1256873%40googlegroups.com.
