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 fixProblem 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 fixComments
APAR information | APAR number | PQ61576 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-05-24 | Closed date | 2002-06-20 | Last modified date | 2002-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 APAR is sysrouted TO one or more of the following:PQ63688PQ63689PQ63690PQ63691PQ63693PQ63694PQ63695PQ63696PQ63697PQ63698PQ63700Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|