PQ61833: PERFORMANCE SERVLET ?REFRESHCONFIG DOES NOT REFRESH AFTER JVM RESTART. | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Performance servlet?refreshConfig=true not working as expected after jvm restart. Existing appserver was deleted, then re- imported with same name. The refreshConfig option fails to display any of the new apppserver topology. No exceptions are detected in logs. Admin server needs to be restarted as a circumvention. WASENG websphere performance servlet pmi refreshLocal fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.0 Users of * * PMI performance servlet and Resource * * Analyzer * **************************************************************** * PROBLEM DESCRIPTION: Performance Servlet(PMI) can't * * refresh the config values after * * creation of the same application * * server with a new configuration. * **************************************************************** * RECOMMENDATION: * **************************************************************** After redeploying appserver using XMLConfig, the performance servlet fails to generate a full topology, only the node information is displayed.Problem conclusion By removing the caching of PMIService bean, this problem no longer occurs.Temporary fix efix is on wasdoc0Comments
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 #: PQ61833
IBM Group: Software Group
Modified date: Jun 17, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.