PQ65178: ON RECOVERY FROM DATABASE DOWN, WAITING THREADS DO NOT THROW CONNECTION WAIT TIMEOUT EXCEPTIONS WHEN WAITING ON THE POOL. | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description On an Oracle down, the connection pool is flushed when the fatal stale connection excption is thrown. When some threads are repopulating the pool, the other threads wait but do not thr ow the proper connection wait timeout after the specified time.Local fix Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server users of * * connection management to connect to a * * relational database. * **************************************************************** * PROBLEM DESCRIPTION: When database server machine fails, * * user does not see * * StaleConnectionExceptions or * * ConnectionWaitTimeoutExceptions as * * expected. * **************************************************************** * RECOMMENDATION: * **************************************************************** A problem existed where requests to open new connections to the database server were serialized. Because the database server has failed, each request must timeout resulting in long wait times (approximately 40 seconds) between exceptions.Problem conclusion Removed synchronization around getConnection requests, causing exceptions to be thrown in a timely manner.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 #: PQ65178
IBM Group: Software Group
Modified date: Sep 5, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.