PQ55659: CAPABILITY TO OVERRIDE ALL FINDBYPRIMARYKEY METHODS READ-ONLY | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description This patch provides an ability to make the container override the read-only setting on all findByPrimaryKey methods to "true". This has the side effect of causing the persister to no longer place the FOR UPDATE clause on the SQL Query for that method. The results of the findByPrimaryKey metod must be used in a new transaction, if the intent is to modify any of the fields in the returned EJB reference.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere 3.5 and earlier customers who * * were accustomed to unchecking the * * "FindForUpdate" checkbox in the System * * Management GUI to indicate that the keyword * * FOR UPDATE clause should not be used by * * the EJB container when EJB findByxxx methods * * are used. * **************************************************************** * PROBLEM DESCRIPTION: In WebSphere 4.0, the default action * * for whether the EJB container should * * include the FOR UPDATE clause in SQL * * query statements on findByxxx methods * * was changed from "no" to "yes." * **************************************************************** * RECOMMENDATION: * **************************************************************** In WebSphere 4.0, the default action for whether the EJB container should include the FOR UPDATE clause in SQL query statements on findByxxx methods was changed from "no" to "yes." This resulted in concurrency problems in some types of applications. The value can be changed by modifying the EJB deployment descriptor, but this was cumbersome for customers with a large number of existing EJBs that depended on the previous function. This fix allows the customer to change the behavior back to the way it worked in version 3.5 and earlier, through a runtime switch.Problem conclusion Applying the WebSphere Application Server efix PQ55659 and following the instructions in the README file will allow customers to obtain the 3.5 default behavior if desired.Temporary fix Code fix provided to wasdoc0\APARs\PQ55659Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ55659
IBM Group: Software Group
Modified date: Jan 4, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.