PQ68510: LOOKUP FAILURES OCCUR ON NAMES RESOLVING TO A SERVER WHEN THE SERVER NAME IS USED IN A CLUSTER AND ELSEWHERE IN THE CELL. | |||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Running distributed trade3 on two clusters, one of which is for Web module and the other one is for EJB module. Node manager, node agents, JMS server, EJB module cluster started successfully without any errors. But Web module cluster had this error: [11/12/02 17:25:01:038 EST] 59054d Helpers W NMSV0605W: A Reference object looked up from the context "java:" with the name "comp/env/ejb/Trade" was sent to the JNDI Naming Manager Reference Factory Class Name: com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory Reference Factory Class Location URLs: <null> Reference Class Name: java.lang.Object Type: JndiLookupInfo Content: JndiLookupInfo: jndiName="cell/clusters/TradeEJB2/Trade"; providerURL=""; initialContextFactory="" Exception data follows: javax.naming.NameNotFoundException: cell/clusters/TradeEJB2/TradeLocal fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users who * * create clusters such that a server in the * * cluster has a name which is not unique * * within the cell. * **************************************************************** * PROBLEM DESCRIPTION: The name space is not constructed * * correctly causing a name not found * * exception. * **************************************************************** * RECOMMENDATION: Apply e-fix for this problem or apply PTF1. * * Alternatively, make sure that server names * * of cluster members are unique within the * * cell. * **************************************************************** The name space is not constructed correctly in certain servers in a cell such that the server name is used as a cluster member and for some other server in the cell. Lookups on these servers may yield incorrect results.Problem conclusion Apply fix to 5.0 or apply fix pack 1 to fix the described problem, or make sure that server names used in clusters are unique within the cell.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 #: PQ68510
IBM Group: Software Group
Modified date: Feb 18, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.