Hello,

Is anyone using Websphere and a datasource without database transactions? This is a typical situation with legacy iSeries database tables.

On an iSeries system there is often a need to perform database updates without using transactions.
The Hibernate property
<property name="connection.isolation">0</property>
appears to specify that database transaction isolation is "none" and that transactions will not be used. However, it appears that this setting is ignored if a connection pool/data source is used, presumeably because the connection pool/data source will control the setting. Websphere 5.1 does not permit transaction isolation to be configured in the connection pool/data source setup, apparently leaving it to the application. The only way we could get this to work, that is, to not use transactions was to execute in Java code connection().setTransactionIsolation(Connection.TRANSACTION_NONE) each time a session is created. Is this OK?

-- Peter


Hibernate version: 3.0.5
Websphere version: 5.1.2