Hi all,

In general, it is recommended to always a commit a session. When using a Hibernate session that performs selects statement only, is it a good idea to just close the session without committing or performing a rollback? Can anybody roughly point out the side effects of not committing the session in this case?

Thanks in advance.

Best regards,
Niko

You should always end a transaction (either commit or roll back), otherwise locks might be held and hinder scalability.

Yes, this is also what I just read this morning, but this case affects metadata locking which is not a common use case. I particularly interested in table/row locks.
So to sum it up, just closing a Hibernate session doesn't trigger anything automatically and leaves resources open?

Regards,
Niko

Hibernate disables auto-commit, so when you obtain a connection, the JDBC driver will also start a database transaction too.
Behind the scenes, when you close the Session, Hibernate will propagate the close to the logical connection too (unless it is a shared Session).
Depending on the JDBC driver, the underlying transaction might nor might not end.

As a rule of thumb, is always better to end the transaction explicitly.

Thank you for this clarification!