PQ74411: Initial context factory not being set properly. | |||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer description of the problem: WAS 500: The naming corbaurlcontext is issuing an error whereby java.naming.factury.initial environment property seems to be overriding the url context factory setup under context.url_pkg_prefixes assigned to com.ibm.ws.naming. When the java.naming.factury.intiial environment property is notLocal fix set then t e program and it associated lookup works. In our application we need to be able to set the java.naming.factury.initiial environment property and still have the program work. It is our understanding based on jndi spi specification from sun microsystems. Section 3.2 states the setting of the java.naming.factury.intiial environment property is independant of the url support. LOCAL FIX:ン NONEProblem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 5.0.0 and * * 5.0.1 users who use corbaloc or corbalname * * URL lookup names for JNDI naming * * operations * **************************************************************** * PROBLEM DESCRIPTION: Support for corbaloc and corbaname URL * * lookup names in the WebSphere JNDI * * implementation does not set the JNDI * * initial context factory property value * * to use the WebSphere initial context * * factory. * **************************************************************** * RECOMMENDATION: * **************************************************************** Support for corbaloc and corbaname URL lookup names in the WebSphere JNDI implementation does not set the JNDI initial context factory property value to use the WebSphere initial context factory. As a result, the current setting for the initial context factory property is used. If the property value happens to be set to some other initial context factory, incorrect JNDI behavior may result.Problem conclusion To fix the problem, set the JNDI initial context factory property value to use the WebSphere initial context factory for corbaurl and corbaname URL support. The fix is in WebSphere Application Server 5.0.2 and higher.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ74411
IBM Group: Software Group
Modified date: Jun 30, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.