APAR status
Closed as program error.
Error description
When using multiple hosts in a PROVIDER_URL, the following error
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server V5 users using *
* Naming *
****************************************************************
* PROBLEM DESCRIPTION: An org.omg.CORBA.BAD_PARAM exception *
* is thrown when using multiple server *
* addresses in a CORBA URL as the value *
* of javax.naming.Context.PROVIDER_URL. *
* This exception is only seen in the *
* Naming trace, but does not cause *
* problem with any JNDI operations. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An org.omg.CORBA.BAD_PARAM exception is thrown when using
multiple server addresses in a CORBA URL as the value of
javax.naming.Context.PROVIDER_URL. This exception is only seen
in the Naming trace, but does not cause problem with any
JNDI operations.
Problem conclusion
To prevent the BAD_PARAM exception, added some code to the
Naming implementation to make the logic for concatenating
multiple server addresses correct.
Temporary fix Comments
APAR information |
APAR number |
PQ91295 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-07-12 |
Closed date |
2004-08-23 |
Last modified date |
2004-09-13 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|