PQ78437: Subsequent adminconsoles fail to load after db test connection hang occurs in another console.

APAR status
Closed as program error.

Error description
Assume that we have a WAS 4.0.x system running, with two admin
GUIs currently up. (Call them GUI1 and GUI2).
In GUI1, the user navigates to one of the DataSource panels, and
clicks on the "Test Connection" button
For whatever reason, the DataSource in question is currently
down, so the "Test Connection" operation hangs there for at
least a while. Note that for now, we are not concerned *why* the
DataSource happens to be down. Clearly, this can happen
sometimes.  We're also not concerned with the fact that GUI1 is
hanging in this case.
For as long as the "Test Connection" operation is hanging in
GUI1, GUI2 and *all other GUIs* also become hung and are unable
to perform any operation. That is clearly unacceptable.
Local fix
Ensure database is up and running prior to making the test
connection.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 4.0.x users who *
*                 use the "Test Connection" operation.         *
****************************************************************
* PROBLEM DESCRIPTION: If the "Test Connection" operation      *
*                      hangs due to unreachable databases,     *
*                      all other administrative clients (eg.,  *
*                      another admin console, another wscp     *
*                      session) hang as long as the client     *
*                      running the "Test Connnection"          *
*                      operation is hung.  No more             *
*                      administrative tasks can be processed.  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The "Test Connection" operation locks up the repository to
retrieve datasource connection properties.  The lock on the
repository is not released until the "Test Connection"
operation is finished.  Hence, other admin clients waiting
to access the repository are blocked and will appear to be
hung as well.
Problem conclusion
Changed the "Test Connection" code to release the repository
lock earlier.  The repository lock is released after it
has retrieved the datasource connection proeprty from the
repository and before it attempts to make a database
connection.  Hence, other admin clients will be able to
access the repository.  The client running the "Test
Connection" operation is the only client that hangs if the
database is not reachable at the time.
Temporary fix
The temporary fix is now available on 
PQ99999 site.
Comments
APAR information
APAR number PQ78437
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-09-12
Closed date 2003-12-01
Last modified date 2003-12-01

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
admin          

Fix information

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ78437
IBM Group: Software Group
Modified date: Dec 1, 2003