Hibernate version:
2.1.8

We observe that our web application, using Hibernate, sets "implicit transactions" on on our MS SqlServer. The result is that the transactions started this way are never closed and lock up the server.

We get similar behavior with jDTS and the MS Driver (jDTS first sets it to off, and then back to on, MS driver just sets it to on).

Who is responsible for setting "implicit transactions" to on? It is not a Hibernate concept, so probably not Hibernate. Or is there a magic mapping to auto commit? Is it the dialect?

Is it the driver? But there are no other complaints, so this would be weird.

Is this something connection pooling does? We are using the built-in Hibernate pooling.

We are experience exactly the same problem. It locks up the "current activity" pane in the SQL Enterprise Manager.