PQ65589: PERFORMING JNDI CALLS WITH LDAP BACKEND CAUSES LDAP QUERIES TO BE TRUNCATED | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() 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=ULocal 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 is sysrouted FROM one or more of the following: PQ65517 APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
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
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.