PQ59279: REMOVING CLONE DOES NOT REMOVE JNDI NAME WITH 4.02 | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Removal of clone from node does not remove JNDI name from naming space. -Create server group -Install Ear into server group -Clone application from server group onto 2 seperate nodes -Verify that namespace exists for clone on each node with dumpNa meSpace utility. -Remove clone from one of the nodes. -Restart admin server on both nodes just to make sure there isn' t an old JNDI name left in cache. -run dumpNameSpace again just to verify that the clone was remov ed from the node in the admin console, but still exists in the J NDI name space. . This worked for the customer at 4.01, but fails on 4.02. I have reproduced the problem on 4.02.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users running * * 4.0.2 or later who remove enterprise apps * **************************************************************** * PROBLEM DESCRIPTION: Removal of application from node does * * not remove JNDI name from naming * * space. * **************************************************************** * RECOMMENDATION: * **************************************************************** When removing enterpriseApp from node, the JNDI name is not removed from the namespace. This can be verified using the dumpnamespace tool. One of the ways to recreate the problem: -Create server group -Install Ear into server group -Clone application from server group onto 2 separate nodes -Verify that namespace exists for clone on each node with dumpNameSpace utility. -Remove application -Restart admin server on both nodes just to make sure there isn't an old JNDI name left in cache. -run dumpNameSpace again just to verify that the application was removed from the node in the admin console, but still exists in the JNDI name space. . This worked for the customer at 4.01, but fails on 4.02.Problem conclusion Application of eFix PQ59279 ensures removing enterpriseApp from node, the associated JNDI name is also removed from the namespace.Temporary fix sent customer eFix, waiting for feedbackComments
APAR is sysrouted FROM one or more of the following: 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 #: PQ59279
IBM Group: Software Group
Modified date: Jul 18, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.