PQ84906: ENTERPRISE APPLICATION REMOVE OPERATION (UN-INSTALL) IS FAILING WITH LARGER APPLICATION. | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Enterprise Application remove operation (un-install) is failing with larger application.This is happening with all admin tools (adminconsole,wscp and XMLConfig import) . Sample environment: 12 enterprise apps with 291 modules between them (many children) . 1.stop the application 2.Right click and select "Remove" 3.Click "Yes" to export option (export "No" did not make any difference) 4.Click "Yes" to remove -The process hung and timed out after 20 minutes (time out value was set to 20 minutes) -some time it never responds . Following errors were noticed with this trace level. com.ibm.ejs.sm.*=all=enabled: com.ibm.ejs.cm.*=all=enabled: com.ibm.ejs.container.*=all=enabled: com.ibm.ejs.jts.*=all=enabled --the transaction timed out before the second EJB module is remo . ModuleBean > ejbRemove CoordinatorIm I WTRN0066W: Transaction com.ibm.ejs.jts.jts.CoordinatorImpl@4027123#tid=860 timed out after 1,200 seconds. . -one particular method that took up a long time to finish: Module.destroySubcontextIfEmpty() -more than 2 minutes elapsed for the destroySubcontextIfEmpty() to finish. [2/13/04 12:47:01:853 EST] 34b4cb ModuleBean > destroySubcontextIfEmpty [2/13/04 12:49:54:370 EST] 34b4cb ModuleBean < destroySubcontextIfEmpty . The destroySubcontextIfEmpty() method is supposed to remove the subcontext of the jndiNames of the EJB module being removed. The jndiNames do not have a subcontext.However,the code ended up listing all jndiNames in the name space that do not have a subcontext.This resulted in the long time needed to execute this call,since EJB calls are invoked to find each jndiName.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.0.x users * **************************************************************** * PROBLEM DESCRIPTION: When removing a large enterprise * * application, the remove fails with a * * transaction time out error. * **************************************************************** * RECOMMENDATION: * **************************************************************** During application uninstall, the jndi context will be cleaned up. For systems with large application, the name space could be large as well, which slows down application uninstall process, causing it to eventually time out.Problem conclusion Modified the uninstall code that removes jndi context to better handle large namespaces, so an application uninstall will not time out.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
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 #: PQ84906
IBM Group: Software Group
Modified date: Jul 12, 2004
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.