PQ61576: BAD PARAM THROWN BY INITIALCONTEXT.LIST(STRING NAME)

A fix is available
WebSphere Application Server Version 3.5 Fix Pack 7 (3.5.7)

APAR

APAR status
Closed as program error.

Error description
After upgrading from WAS AE 3.5.3 to 3.5.6 on Sun Solaris,
InitialContext.list(String name) method throws
CNNameEnumera D CNNameEnumeration: SystemException:
org.omg.CORBA.BAD_PARAM:CNNameEnumera D CNNameEnumeration: SystemException:
org.omg.CORBA.BAD_PARAM: minor code: 1 completed: Maybe
org.omg.CORBA.BAD_PARAM:org.omg.CORBA.BAD_PARAM: minor code: 1 completed: Maybe
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 3.5.5           *
*                 and 3.5.6 users of Oracle as a repository    *
****************************************************************
* PROBLEM DESCRIPTION: A org.omg.CORBA.BAD_PARAM exception     *
*                      was thrown with context.list() method   *
*                      when the output of such method          *
*                      contains JNDI contexts which were       *
*                      created under WebSphere Application     *
*                      Server 3.5.5 or 3.5.6 with Oracle as    *
*                      its repository.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a JNDI naming context was created under WebSphere
Application Server 3.5.5 or 3.5.6, an empty string was
set as the class name for those newly created context, other
than "javax.naming.Context". The empty string is stored as it
is in most of databases, exception Oracle, which maps the
empty string to null.

The naming client will get the "org.omg.CORBA.BAD_PARAM"
exception when the list() method is performed on any context
which contains the contexts that have null as its class name.
That will be true to all 3.5.6, pre 3.5.6, 4.0.3 and pre 4.0.3
naming client.
Problem conclusion
The problem was caused by the fact that an empty string was set
as class name for newly created JNDI context in the JNDI
naming implementation.

With this APAR, the proper class name, which is
"javax.naming.Context", is set for newly created JNDI contexts.
That should prevent null stored as class name in Oracle database
since it maps an empty string to null, which definitely will
cause "org.omg.CORBA.BAD_PARAM" exception when the list()
method is performed on any context which has such newly
created context as its child.
Temporary fix
Comments
APAR information
APAR numberPQ61576
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-05-24
Closed date2002-06-20
Last modified date2002-07-30

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:

PQ63688PQ63689PQ63690PQ63691PQ63693PQ63694PQ63695PQ63696
PQ63697PQ63698PQ63700

Modules/Macros
NAMING
APAR is sysrouted TO one or more of the following:PQ63688PQ63689PQ63690PQ63691PQ63693PQ63694PQ63695PQ63696PQ63697PQ63698PQ63700Modules/Macros

Fix information
Fixed component nameWAS ADVANCED AI
Fixed component ID5648C8400

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ61576
IBM Group: Software Group
Modified date: 2002-07-30