Mapping between WebSphere® Application Server access intent and IBM® DB2® isolation level
 Technote (troubleshooting)
 
Problem(Abstract)
In WebSphere Application Server V5 releases, access intent policies are specified for Entity Beans and Entity Bean methods to optimize the database persistence. The Access Intent policy determines the JDBC™ Isolation Level that is used by the WebSphere Persistence Manager. This document identifies the isolation level used by DB2 for each access intent policy.
 
Resolving the problem
The following table shows the JDBC isolation level and the DB2 isolation level for each WebSphere Application Server Access Intent policy.
WebSphere Application Server Access Intent
JDBC Isolation Level
IBM DB2 Isolation Level
  • wsPessimisticUpdate- Weakest LockAtLoad
  • wsPessimisticUpdate
  • wsPessimisticRead
TRANSACTION_REPEATABLE_READ
Read Stability (RS)
  • wsOptimisticUpdate
  • wsOptimisticRead
  • wsPessimisticUpdateNo-
    Collisions
TRANSACTION_READ_COMMITTED
Cursor Stability (CS)
  • wsPessimisticUpdate- Exclusive
TRANSACTION_SERIALIZABLE
Repeatable Read (RR)
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Data & Information Management DB2 Universal Database for Linux, UNIX and Windows Application Programming - JDBC Platform Independent 8, 7 Edition Independent
Data & Information Management DB2 Connect
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > EJB Container
Operating system(s): Windows
Software version: 5.1.1
Software edition:
Reference #: 1162747
IBM Group: Software Group
Modified date: Feb 16, 2005