Vert.x JDBC client transaction rollback behavior when enabling maxTransactionTime in 4.3.x

Determine whether enabling the maxTransactionTime option in Vert.x 4.3.x causes the JDBC client to automatically roll back any transaction left open when a connection is returned to the pool after a database backup restore.

Consider that the client defaults to auto‑commit mode, does not expose a hook for abandoned connections, and that maxTransactionTime only aborts transactions after a configured threshold, leaving uncertainty about its effect on connection‑return scenarios.

Does enabling maxTransactionTime trigger a rollback on connection return, or must developers still provide explicit cleanup? If it does not, what configuration or pattern ensures consistent reads after a restore? Are there any risks to long‑running backup verification jobs when setting a low threshold?