Guidelines for DB2 settings for WebSphere concurrency control management

If your installation uses typical DB2 defaults for U-lock management and lock size, certain WebSphere applications that use container-managed Enterprise beans (CMP beans) may encounter deadlocks. The likelihood of encountering deadlocks is entirely dependent on the design and execution pattern of the application. The potential for deadlocks increases with the number and frequency of applications driving concurrent transactions that update the same areas of the DB2 database. If, given your installation's application workload, the potential for deadlocks is high, consider using the following DB2 settings:

For additional details, see the information about settings for the internal resource lock manager (IRLM) in DB2 Installation Guide.

Alternative: Your applications may qualify for the optimistic approach to concurrency control management. To determine whether your applications can use optimistic concurrency control, see the topic about controlling concurrent access to persistent data in the assembling applications information in the z/OS view of the WebSphere Application Server information center, which you can access via the WebSphere Application Server for z/OS library Web site.




Searchable topic ID:   cinsdb2concurmgmt
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/cins_db2concurmgmt.html

Library | Support | Terms of Use | Feedback