PQ59960: ADMINSERVER FAILS TO RECONNECT TO DATABASE WHEN DATADASE IS RECYCLED. | |||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
APAR status Closed as user error. Error description Recreate steps were as such: Connected Nodea to remote oracle database. Ran Hit count and connection pool test against WAS repository. Recycled database server and could not hit Enterpris Java bean, or connection pool test servlet. Performed a net stop on adminserver successfully. Java process's still were present and never were killed. Performed net start unsuccessfully. Kille d all java processes, performed netstart successfully. Customer seeks not haveing to ever have to recycle adminserver. No down time.Local fix Problem summary Problem conclusion Temporary fix Comments The AdminServer does reconnect to database if the database is back up and running after disconnected. The adminserver won't reconnect to the db if the db is down. The "net stop" cannot stop all java processes including application server and admin server processes successfully since it goes through the DrAdminServer code path (AEs) which is not supported on AE. The suggestion is to use WSCP "Node stop" or "Node stop - force" to stop the java processes.
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 #: PQ59960
IBM Group: Software Group
Modified date: May 1, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.