PQ61833; 4.0.2,4.0.3: Performance Servlet (PMI)
cannot refresh the config values
Downloadable files
Abstract
After redeploying WebSphere® Application Server using
XMLConfig, the performance servlet fails to generate a full topology, only
node information is displayed.
Download Description
PQ61833 resolves the following problems:
Performance servlet?refreshConfig=true not working as
expected after Java™ Virtual Machine (JVM™) restart. Existing Application
Server was deleted, then re-imported with same name. The refreshConfig
option fails to display any of the new Application Server topology. No
exceptions are detected in logs. Administrative server needs to be
restarted as a circumvention. This problem also exists in Resource
Analyzer.
USER SCENARIO:
When invoking performance servlet with arguments
?refreshConfig=true, the output is not what is expected after
restarting the application server. Existing Application Server was
deleted, then re-imported with same name. The refreshConfig option fails
to display any of the new WebSphere Application Server topology.
PROBLEM DESCRIPTION:
Performance Servlet (PMI) cannot refresh the config values after creation
of the same Application Server with a new configuration.
SOLUTION:
PQ61833 removes the caching of PMIService bean, this problem no longer
occurs.
SUPERSEDES:
PQ61833 supersede PQ59321.
Prerequisites
none
Installation instructions
Please view the readme.txt file for detailed installation
instructions