Requirements for setting data access isolation levels
You can set the isolation levels for data access components that comprise Enterprise JavaBeans (EJB) 2.x and later modules.
In an EJB 1.1 module, you can set the isolation level at the method level or bean level. This capability also applies to container-managed persistence (CMP) 1.1 beans that you assemble into EJB 2.x modules. WebSphere® Application Server permits the deployment descriptor of a CMP bean to declare the version level of 1.1, regardless of the overall module version.
However, the ability to set isolation level at the method or bean level does not apply to other enterprise beans within an EJB 2.x module, including CMP 2.x beans. WebSphere Application Server Version 5.0 removed this capability from EJB 2.0 modules to deliver an architecture that ultimately provides more efficient connection use.
- You cannot specify isolation level on the EJB method level or bean level.
- If you configure a JDBC application, a bean-managed persistence (BMP) bean, or a servlet to participate in global transactions, any connection that is shared cannot accept a user-specified isolation level. WebSphere Application Server can only set a user-specified isolation level on a connection that is not shared within a global transaction. Generally, you want to refrain from specifying isolation levels on shareable connections.
- Isolation level on connections used by 2.x CMP beans
- In a EJB 2.x module, when a CMP 2.x bean uses a new data source to access a backend database, the isolation level is determined by the WebSphere Application Server run time, based on the type of access intent assigned to the bean or the calling method. Other non-CMP connection users can access this same data source and also use the access intent and application profile support to manage their concurrency control.
- Connections used by other 2.x enterprise beans and other non-CMP components
- For all other JDBC connection instances (connections other than
those used by CMP beans), you can specify an isolation level on the
data source resource reference. For shareable connections that run
in global transactions, this method is the only way to set the isolationLevel for
connections. Trying to directly set the isolation level through the setTransactionIsolation() method
on a shareable connection that runs in a global transaction is not
allowed. To use a different isolation level on connections, you must
provide a different resource reference. Set these defaults through
your assembly tool.
Each resource reference associates with one isolation level. When your application uses this resource reference Java™ Naming and Directory Interface (JNDI) name to look up a data source, every connection returned from this data source using this resource reference has the same isolation level.
Components needing to use shareable connections with multiple isolation levels can create multiple resource references, giving them different JNDI names, and have their code look up the appropriate data source for the isolation level they need. In this way, you use separate connections with the different isolation levels enabled on them.
It is possible to map these multiple resource references to the same configured data source. The connections still come from the same underlying pool, however; the connection manager does not allow sharing of connections requested by resource references with different isolation levels. Consider the following scenario:- A data source is bound to two resource references: jdbc/RRResRef and jdbc/RCResRef.
- RRResRef has the RepeatableRead isolation level defined. RCResRef has the ReadCommitted isolation level defined.
The product does not require you to set the isolation level on a data source resource reference for a non-CMP application module. If you do not specify isolation level on the resource reference, or if you specify TRANSACTION_NONE, the WebSphere Application Server run time uses a default isolation level for the data source. Application Server uses a default setting based on the JDBC driver.
For most drivers, WebSphere Application Server uses an isolation level default of TRANSACTION_REPEATABLE_READ. For Oracle drivers, however, Application Server uses an isolation level of TRANSACTION_READ_COMMITTED. Use the following table for quick reference:
Database: Default isolation level: DB2® RR Oracle RC Sybase RR Informix® RR Apache Derby RR SQL Server RR Note: These same default isolation levels are used in cases of direct JNDI lookups of a data source.- RR = JDBC Repeatable read (TRANSACTION_REPEATABLE_READ)
- RC = JDBC Read committed (TRANSACTION_READ_COMMITTED)
To customize the default isolation level, you can use the webSphereDefaultIsolationLevel custom property for the data source. In most cases you should define the isolation level in the deployment descriptor when you package the EAR file, but in certain situations you might need to customize the default isolation level. This property will have no effect if any of the previous options are used, and this custom property is provided for those situations in which there is no other means of setting the isolation level.
Use the following values for webSphereDefaultIsolationLevel custom property:
To define this custom property for a data source:Possible values JDBC isolation level DB2 isolation level 8 TRANSACTION_SERIALIZABLE Repeatable Read (RR) 4 (default) TRANSACTION_REPEATABLE_READ Read Stability (RS) 2 TRANSACTION_READ_COMMITTED Cursor Stability (CS) 1 TRANSACTION_READ_UNCOMMITTED Uncommitted Read (UR) TRANSACTION_NONE No Commit (NC) - Click .
- Click Data sources in the Additional Properties section.
- Click the name of the data source.
- Click Custom properties.
- Create the webSphereDefaultIsolationLevel custom property.
- Click New.
- Enter webSphereDefaultIsolationLevel for the name field.
- Enter one of the possible values in the value field.
- Resource reference isolation level
- Isolation level that is specified by the access intent policy
- Custom property that configures an isolation level
- Application Server's default setting.