PQ65589: PERFORMING JNDI CALLS WITH LDAP BACKEND CAUSES LDAP QUERIES TO BE TRUNCATED

 A fix is available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)



APAR status
Closed as program error.

Error description
Environment:
WebSphere Application Server (WAS) 4.0.2 AE for Solaris
.
Description:
   Customer is performing JNDI calls within their application
and using LDAP as the backend. They notice that WAS JNDI is
truncating queries to the LDAP server. WAS naming trace shows
the following excerpt indicating the truncation:
.
[8/21/02 11:26:32:820 CEST]   70856b WsnLdapContex E ne =
parentDirCtxsearch(newDirCtxRdn, "objectClass=*", sc);
                                 parentDirCtx:
                                 newDirCtxRdn:
ibm-wsnName=TLSDEVL,ibm-wsnName=domainRoots,ibm-wsnTree=t1,o=WA
Naming,c=U
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WhebSphere Application Server v4.0.1,        *
*                 v4.0.2, v4.0.3, and v4.0.4 users, who use    *
*                 the J2EE or pure Jave client to connect to   *
*                 WebSphere Application Server for zOS         *
*                 and OS/390.                                  *
*                                                              *
****************************************************************
* PROBLEM DESCRIPTION: The JNDI naming implementation has      *
*                      truncated the last character of a       *
*                      lookup name for a linked context.       *
*                      Users may see a                         *
*                      javax.naming.NameNotFoundException      *
*                      when they perform JNDI operation with   *
*                      in a J2EE or pure Java client and       *
*                      using LDAP as the backend repository.   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Last character of a lookup name for a linked context was
truncated in JNDI naming implmentation over LDAP. This could
result in a javax.naming.NameNotFoundException when a JNDI
call is performed within a J2EE or pure Java client and
using LDAP as the backend repository.
Problem conclusion
With the fix, the last character of a lookup name for a linked
context is no longer being truncated when a WebSphere J2EE or
pure Jave client performs the JNDI calls over a WebSphere
Application Server for zOS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ65589
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-08-26
Closed date 2002-08-30
Last modified date 2002-10-17

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

APAR is sysrouted TO one or more of the following:

Modules/Macros
NAMING          

SRLS

Fix information
Fixed component name WEBSPHERE AE SO
Fixed component ID 5630A2202

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ65589
IBM Group: Software Group
Modified date: Oct 17, 2002