PQ75057: JNDI lookups of any non-context objects on WebSphere 3.5.x or non-WebSphere server fail with a NamingException | |||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description JNDI lookups resolving to EJB homes or any othernon-context objects directed to WebSphere version 3.5.x or non-WebSphere servers fail with a NamingException. The text of the NamingException message is "Unexpected exception." Lookups on WebSphere servers version 4.0.x or above function normally.Local fix This problem was introduced in the update, WAS_Naming_04-17-2003_5.0.1_cumulative_Fix. Any WebSphere 5.0.1 Naming update subsequent to it (e.g., WAS_Naming_05-20-2003_5.0.1_cumulative_Fix) contains the fix for this problem.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 5.0.1 users who * * have applied the Naming cumulative fix * * update #1: * * WAS_Naming_04-17-2003_5.0.1_cumulative_Fix * **************************************************************** * PROBLEM DESCRIPTION: Lookups resolving to EJB homes or any * * other non-context objects directed to * * WebSphere version 3.5 or non-WebSphere * * servers fail with a NamingException. * **************************************************************** * RECOMMENDATION: * **************************************************************** Lookups resolving to EJB homes or any other non-context objects directed to WebSphere version 3.5 or non-WebSphere servers fail with a NamingException. The text of the NamingException message is "Unexpected exception". Lookups directed to WebSphere servers running on version 4.0 or above function normally.Problem conclusion This problem is the result of a bad cumulative-fix. The file which contains the original fix is good, but the Naming cumulative fix update #1 (WAS_Naming_04-17-2003_5.0.1_cumulative_Fix) did not include the right version of that file. So the Naming cumulative update #1 itself is bad. To fix the problem, include the right version of that file in the Naming cumulative fix update #2, WAS_Naming_05-20-2003_5.0.1_cumulative_Fix.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: 00W
Software edition:
Reference #: PQ75057
IBM Group: Software Group
Modified date: Jun 27, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.