Servlets that connect to DB2 get a default JDBC isolation level of TRANSACTION_REPEATABLE_READ
 Technote (FAQ)
 
Problem
The default JDBC® isolation level given to servlets that connect to DB2® is not documented in "WebSphere® Application Server V4.0.1 for z/OS® and OS/390®: Assembling J2EE Application."
 
 
Solution
Chapter 4 of WebSphere Application Server V4.0.1 for z/OS and OS/390: Assembling J2EE Applications, SA22-7836-06 will be updated, The note following the isolation level default value in the section "Isolating transactions that access persistent data" will be changed to the following:

Notes:

1. For beans assembled and deployed with the default descriptor value TRANSACTION_NONE, WebSphere Application Server for z/OS uses the JDBC isolation level TRANSACTION_REPEATABLE_READ on connections that the Enterprise JavaBean™ (EJB) container acquires and uses to manage CMP persistent state in DB2.
2. Servlets do not have a descriptor value for isolation levels. Therefore, servlets that connect to DB2 will also get a default JDBC isolation level of TRANSACTION_REPEATABLE_READ.

NOTE: Periodically, we refresh the documentation on our Web site, so these changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at URL:

http://www.ibm.com/software/webservers/appserv/zos_os390/library/
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Publications
Operating system(s): z/OS
Software version: 4.0.1
Software edition:
Reference #: 1137194
IBM Group: Software Group
Modified date: Aug 2, 2004