PQ76254: WEBSPHERE ALLOWS CREATION OF MULTIPLE DATA SOURCES WITH SAME JNDI NAME

 Fixes are available

5.1.0.5: WebSphere Application Server V5.1.0 Cumulative Fix 5
5.1.1: WebSphere Application Server Version 5.1 Fix Pack 1 (Version 5.1.1)



APAR status
Closed as program error.

Error description
On WAS 5.0.x, user can create data souces with identical JNDI
JNDI Name. The data sources are created from different
JDBC Providers (i.e. different Helper class).
.
To reproduce the problem:
1. Create 2 JDBC Providers: "DB2 JDBC Provider" and "Oracle
JDBC Thin Driver"
.
2. Under the "DB2 JDBC Provider", create v5 data source with
   Name      = V5_db2ds
  JNDI Name = jdbc/V5_db2ds
and specify the Custom Properties for the data source
.
3. Under the "Oracle JDBC Thin Driver", create v5 data source
with
   Name      = newDS
   JNDI Name = jdbc/V5_db2ds
and specify the Custom Properties for the data source (maily
URL)
.
As you can see, the 2 data sources "V5_db2ds" and "newDS" have
same JNDI name "jdbc/V5_db2ds". There is no error when creating
these two data sources.
.
The output from dumpNameSpace only gives the one for "NewDS".
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Users of the WebSphere Application Server    *
*                 who configure data sources.                  *
****************************************************************
* PROBLEM DESCRIPTION: Configuration validation allows data    *
*                      sources with duplicate JNDI names.      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Configuration validation allows data sources with duplicate JNDI
names.  That is, a resources document (resources.xml) allows for
a collection of resource provides, each of which having a list
of resource factories.  (Several types of resource factories are
available, including data sources.)  Each resource factory has
a name and a JNDI name.  Validation should generate an error
whenever a factory name or factory JNDI name is duplicated
(beneath a single resource provider).  Case is not considered
when comparing factory names, but is considered when comparing
factory JNDI names.

This problem may appear whenever data sources are configured.

The fix adds two new validations, one for factory name, and one
for factory JNDI name.  The following messages provide an
example
of the concrete messages that may be generated.  (The following
output was generated by 'wsadmin' and '$AdminConfig validate'.)

WASX7190I: Validation at level HIGHEST with cross-document
validation enabled, requested at Sep 3, 2003 5:18:44 PM for
action "validate"

WASX7195I: Severity 1; line 0; target "Websphere:_Websphere_
Config_Data_Display_Name=WebSphere JMS Provider,
_Websphere_Config_Data_Type=JMSProvider,_Websphere_Config_
Data_Id=cells/CALLY-PLUS/nodes/CALLY-PLUS:resources.xml#
builtin_jmsprovider"; CHKW3050E: Duplicated resource
 factory name PLANTSBYWEBSPHEREQ.  Another resource factory
 already has this name.  (The names of resource factories
 beneath a single resource provider must be distinct.)

WASX7195I: Severity 1; line 0; target "Websphere:_Websphere_
Config_Data_Display_Name=WebSphere JMS Provider,
_Websphere_Config_Data_Type=JMSProvider,_Websphere_Config_
Data_Id=cells/CALLY-PLUS/nodes/CALLY-PLUS:resources.xml#
builtin_jmsprovider"; CHKW3051E: Duplicated resource
 factory JNDI name plantsby/InvQ.  Another resource factory
 already has this JNDI name.  (The JNDI Names of resource
 factories beneath a single resource provider must be
distinct.)
Problem conclusion
The fix adds two new validations, one for factory name, and one
for factory JNDI name.
An installable fix is provided.
Temporary fix Comments
APAR information
APAR number PQ76254
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-07-11
Closed date 2003-11-12
Last modified date 2004-04-08

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ76254
IBM Group: Software Group
Modified date: Apr 8, 2004