PQ54156: USE URL CONTEXT IMPLEMENTATION, A JNDI FEATURE | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description This APAR is to address two issues in WebSphere Application Server 4.0. 1) allow user to configure LDAP search time limit in milliseconds. 2) use JNDI's feature, URL Context Implemetation. A URL context implementation is a context that can handle arbitrary URL strings of the URL scheme supported by the context. The JNDI automatically searches for the URL context implementation. If the URL context implementation is not found, it will use only the implementation specified by the environment properties (if any)Local fix Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server users who * * perform user authentication against Ldap * * cluster. * **************************************************************** * PROBLEM DESCRIPTION: While performing a user authentication * * against an Ldap cluster, the user may * * experience an unexpected long login * * process, or user receives unexpected * * authentication failure after a long * * delay. * **************************************************************** * RECOMMENDATION: See Efix's readme.txt for detail. Only * * users using Ldap clusters need this efix. * **************************************************************** While performing authentication against Ldap cluster(via IP sprayer, DNS round-robin, etc), WebSphere may experience long login process, or unexpected authentication failure after long delay, or even result in browser hang. WebSphere reuses the same initial context and the same network connection, which works fine for single ldap server. To use ldap cluster, WebSphere has to make new connections.Problem conclusion While performing Ldap search operations, WebSphere reuses the same initial context and the same network connection, which works fine for single ldap server. To perform search in a ldap cluster, WebSphere can not reuse the same connection, and has to make new connections since a search may be routed to different servers.Temporary fix yes. Efix PQ54156_eFix.jar is created.Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ54156
IBM Group: Software Group
Modified date: Apr 24, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.