PQ60281: NULLPOINTEREXCEPTION _INSTEAD OF_ STALECONNECTIONEXCEPTION: CACHEDSTATEMENT.CLOSE() IS CALLED AFTER CACHEDSTATEMENT.DESTROY | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description A NullPointerException is generated where a StaleConnectionException is expected. This is caused due to the fact that in certain scenarios CachedStatement.close() is called after CachedStatement.destroy, and CachedStatement.close() does not perform a null test on the "currentBitSet" attribute before it is dereferenced.Local fix Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server users * * of Connection Manager. * **************************************************************** * PROBLEM DESCRIPTION: Users could see a NullPointerException * * in certain scenarios during a close * * on a preparedStatement. * **************************************************************** * RECOMMENDATION: * **************************************************************** There were scenarios where the statement was already destroyed before close was called, destroy nulled a variable which was used by close, resulting in NullPointerException.Problem conclusion Having this scenario occur is innocuous, so now the variable is checked before using it, thus avoiding the NullPointerException.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
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ60281
IBM Group: Software Group
Modified date: Apr 30, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.