PQ71169: EAR UNINSTALL NOT REMOVING THE JNDI BINDINGS FROM REPOSITORY

 Fixes are available

4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6
PQ84906; V4.0.5-V4.0.7: Application remove operation fails with large app.
System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5



APAR status
Closed as program error.

Error description
Enterprise Application Un-Installis not removing all the
JNDI bindings related to the ear.During the next install
admin console displays an option to override these bindings.
(but XMLConfig not having this option)
.
"Un-Install" of ear(Enterprise Application) must clean all the
JNDI referencesfrom the repository (related to that ear)
irrespective of override option during next install.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: For WebSphere Application Server 4.0 users   *
****************************************************************
* PROBLEM DESCRIPTION: Enterprise Application Un-Installis     *
*                      not removing all the JNDI bindings      *
*                      related to the ear. During the next     *
*                      install admin console displays an       *
*                      option to override these bindings.      *
*                      (XMLConfig doesn't have this option)    *
*                                                              *
*                      "Un-Install" of ear (Enterprise         *
*                      Application) must clean all the         *
*                      JNDI references from the repository     *
*                      (related to that ear) irrespective of   *
*                      override option during next install.    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
According to WebSphere Application Server 4.0 design, the ejb
jndi name such as /rules-st/com/fdr/rules/ejb/entity/Addition
are bound/unbound to name space (BindingBeanTable) when
starting/stopping an application.  However, the jndi unbind
function does not remove (clean) the sub-context of EJB JNDI
names such as /rules-st/com/fdr/rules/ejb/entity that have been
created on BindingBean table (name space) when the application
is started. These sub-context of jndi names have never been
destroyed from the name space when the EJBs are removed.

This APAR is opened to clean all naming sub-context (prefixes)
from the name space when uninstalling the application and
assumes that the jndi names are unbound from the name space
at the time of uninstalling.  The user needs to make sure to
stop the application first before removing the application.
Problem conclusion
This fix adds extra logic to destroy naming sub-context of
jndi names from the name space at ejbRemove() function on
ModuleBean.java. It is assumed that user stops the application
before uninstalling the application.  The test scenario
will be:

1. Install application
2. Start application
3. Stop application
4. Uninstall application
5. Reinstall same application
Temporary fix
The stand-alone test fix was sent to the customer on Mar. 6.
The formal fix is incorporated in the SM cumulative efix
03-12-2003.
Comments
APAR information
APAR number PQ71169
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-02-19
Closed date 2003-04-11
Last modified date 2003-04-11

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
ADMINSVR          

SRLS

Fix information

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ71169
IBM Group: Software Group
Modified date: Apr 11, 2003