PQ70860: SM: Problems administering datasources when a node is down

 A fix is available

4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6



APAR status
Closed as program error.

Error description
In a multi-node WebSphere environment, if a node specified in
one of the JDBC Provider entries is down, users trying to
administer datasources may experience erroneous error messages
on the console, stack traces in the tracefile, and may not be
able to create datasources using the datasource wizard in the
admin console.  There are also additional misbehaviors in the
admin console in this situation.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application           *
*                 Server 4.0                                   *
****************************************************************
* PROBLEM DESCRIPTION: In a multi-node environment, if user    *
*                      tried to administer a datasource with   *
*                      one or more nodes down, exceptions      *
*                      may be seen in the tracefile and parts  *
*                      of some admin console panels will be    *
*                      missing.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This problem only occurs in a multi-node (single repository)
environment.  Depending on how datasources were installed and
which node initially created the repository, the symptoms of
the problem may vary.  Basically, the root problem is due to
improper processing of the exception thrown when a remote node
is down - the recovery attempt was somewhat less than elegant.
Problem conclusion
Modified code to check to see whether remote node is active
before relying on it to provide information.  Also modified
some code paths so that, instead of just giving up (and,
hence not giving info needed to create admin console panels),
we recover and return to the correct code path.
Temporary fix
Test fix for PQ70860 placed on 
pq99999.raleigh.ibm.com approx.
1
1:45 AM (CST) on 17Mar03.  Had to specify names of L2 persons
w
h
o could distribute fix so gave:
   tdwatts@us.ibm.com (Tami
k
o)
  bhalodi@us.ibm.com (Ajay)
decour@us.ibm.com (Tim D.)
Comments
APAR information
APAR number PQ70860
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-02-11
Closed date 2003-04-03
Last modified date 2003-04-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
AdminSVR          

SRLS

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 #: PQ70860
IBM Group: Software Group
Modified date: Apr 3, 2003