PK74850: CORBANAME URL CONTAINING CHARACTER "." AND "#" DOES NOT BIND INTO THE NAMESPACE CORRECTLY AND CAUSES THE LOOKUP TO FAIL.

Fixes are available

APAR status

Closed as program error.

Error description

When the name server changed the way handling bindings created
with a corbaname URL, it does not decode the RFC2396 encoded
format of the stringified name in the URL. By not decoding the
name, names with multiple dots would be rejected because the
required escape character (\) was not recognized in its
encoded format of %5C. This caused org.omg.CORBA.BAD_PARAM
exception or NameNotFoundException.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server V7.0 users of  *
*                  JNDI                                        *
****************************************************************
* PROBLEM DESCRIPTION: Corbaname URL containing "." or "#"     *
*                      does not get bound into namespace       *
*                      properly and causes the lookup to fail  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This problem has to do with the way name server handles
bindings created with a corbaname URL.  This includes
configured enterprise bean bindings and configured CORBA
bindings. The name server used to pass the entire corbaname to
the ORB, which expected the RFC2396 encoded format of the
stringified name in the URL (the part after the first #).
When you pass a corbaname URL to the ORB, it effectively gets
the initial context with the part before the # and performs a
lookup on the stringified name.  Then we made a change in
WebSphere Application Server 6.1 feature pack to split the URL
and pass only the part before the # to the ORB, which returned
the initial NamingContext.  The name server performs the
lookup on the stringified name.  We needed to decode the name
before doing so.  By not decoding the name, names with
multiple dots would be rejected because the required escape
character (\) was not recognized in its encoded format of %5C.
(A name with one dot would not be rejected for syntax
reasonss, but would result in a NotFound exception.)

Problem conclusion

The name server decodes the RFC2396 encoded format of the
stringified corbaname URL containing during binding.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.1.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK74850
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-31
Closed date
2008-11-18
Last modified date
2009-02-20

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

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK74850: CORBANAME URL CONTAINING CHARACTER "." AND "#" DOES NOT BIND INTO THE NAMESPACE CORRECTLY AND CAUSES THE LOOKUP TO FAIL.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?