PQ54167: OPTION A CACHING IS NOT WORKING ON 401 AE | |||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description Option A caching is not working on AE at the 401 level This was working on AEs 4.0. They are seeing ejbload being called on every call of their ejb. The failure is occurring with the transaction attribute of notsupported.Local fix Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server 4.0.1 and * * 4.0.2 users * **************************************************************** * PROBLEM DESCRIPTION: Option A caching not working correctly. * **************************************************************** * RECOMMENDATION: * **************************************************************** Even when using option A caching for an EJB, the user is seeing ejbload() being issued for every method call on the EJB. This is caused when, during after_completion() in the CoordinatorImpl class, each registered Synchronization object is called to perform after_completion with the incorrect boolean status.Problem conclusion CoordinatorImpl will be changed to correct the problem.Temporary fix Comments
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 #: PQ54167
IBM Group: Software Group
Modified date: Nov 5, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.