PMI application is slow to return requested data if queryConfigObjects is called without narrowing the scope of the call
 Technote (troubleshooting)
 
Problem(Abstract)
When designing and writing applications to use the PMI (Performance Monitoring Interface) API to get configuration information, if the queryConfigObjects() call is made without proper parameters, it could adversely affect performance in a large cluster or DMgr configuration.
 
Cause
The cause of the problem could be how the call is made to queryConfigObjects. Limit the data that this call retrieves to the Application Server or Node Agent that you need to get data from.
 
Resolving the problem
The solution is to provide, where possible, the Application Server or Node Agent name in the call.

So, rather than make this call:
oList = getConfigService().queryConfigObjects(null, null, typeON, null);

Make a call like the following:
oList = getConfigService().queryConfigObjects(null, scopeON, typeON, null);
where scopeON is the name of the Application Server or Node Agent.

See this link for more details on the PMI and JMX interfaces
http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.
base.doc/info/aes/javadoc/ae/com/ibm/websphere/pmi/package-summary.html

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > PMI/Performance Tools
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1224489
IBM Group: Software Group
Modified date: Dec 4, 2005