H2 community: I have created a feature enhancement request to allow for H2 users to be able to specify various TCP connection parameters, including connectionTimeout, keepAlive, send/recvTimeout (or soTimeout for both) in order for H2 to handle TCP connection health. As a matter of comparison, most RDBMS systems support exposing theses settings for configuration.
Currently, H2 utilizes infinite connection timeout values, which may lead to deadlocks and H2 users would benefit from having a reasonable default, and configurable setting in order to prevent that from happening. I've drafted proposed features, use cases and behaviors here: https://github.com/h2database/h2database/issues/2032 Questions, comments and feedback are most welcome. Thank you, Matt Pavlovich -- 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/c2d44592-d47c-4f76-bb36-3868a4766994%40googlegroups.com.
