PQ79103: CONNECTION MANAGER RETURNED NULLPOINTEREXCEPTION WHEN EXPECTED STALECONNECTIONEXCEPTION TO BE RETURNED | |||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description When the physical connection to the database became bad for some reason, application expects to get StaleConnectionException but it gets the NullPointerException instead.Local fix Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server users who * * use Connection Pooling. * **************************************************************** * PROBLEM DESCRIPTION: A small window existed where a * * NullPointerException would * * be returned instead of a * * StaleConnectionException. * **************************************************************** * RECOMMENDATION: * **************************************************************** A window existed whereby if a connection to the database went bad during a user transaction, We try to rollback a connection which has already been rolled back.Problem conclusion We added a check so we would not try and rollback the connection twice.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: PQ78561 APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ79103
IBM Group: Software Group
Modified date: Oct 1, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.