A deadlock occurs when connecting to DB2® on S/390 using container-managed persistence (CMP) enterprise beans
 Technote (troubleshooting)
 
Problem(Abstract)
A deadlock or data integrity problem can occur when using WebSphere® Application Server V5 CMP enterprise beans to access DB2® on a S/390® (zSeries®) platform. The deadlock occurs if the incorrect DataStoreHelper class is defined for the data source that is used by the CMP enterprise beans.
 
Cause
When deploying CMP enterprise beans to access DB2 on S/390, the deploy tool generates four different SELECT... FOR UPDATE syntaxes for the finder methods that are specific to the S/390 mainframe. The correct method to use is determined by the AccessIntent class, which is resolved at runtime. If you use an incorrect DataStoreHelper class, the incorrect syntax is used and the deadlock occurs.
 
Resolving the problem
To prevent a deadlock or a data integrity problem, use the correct class:
com.ibm.websphere.rsadapter.DB2390DataStoreHelper
for the Datasource Helper Classname value of the data source used by the CMP enterprise beans.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Data & Information Management DB2 for OS/390
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > DB Connections/Connection Pooling
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1157945
IBM Group: Software Group
Modified date: Oct 26, 2004