HP Web Jetadmin - Performance and Threadpools in HP Web Jetadmin

NOTE On 32-bit systems, never attempt to edit this file. 32-bit operating systems are not equipped to
handle any increase in threads.
HP recommends monitoring the performance threads page under the IInstrumentable page as each
default value is updated. Look for large numbers of queued where running is equal to max. Increasing
these values might increase performance and cause other threadpools to back up.
MOAB IInstrumentable Page
To understand threadpools, one must first understand a critical piece of architecture called Managed
Object Abstraction (MOAB) in HP Web Jetadmin. After nodes are discovered during a discovery,
MOAB further processes the nodes to determine if they are devices. MOAB is more or less
responsible for getting and setting information on devices. It manages device communication, trying
to reduce it where possible by keeping a local cache of data and thresholds for how fresh the data
should be. MOAB also manages grouping requests to devices. MOEs are the individual requests that
MOAB issues.
The first place to look when MOAB is running slow is on the IInstrumentable page found by adding
/instrumentable to the HP Web Jetadmin URL in a browser.
The purpose of using this page is to look for backed up threads. Under the Threads link, if the line
WorkerThreadPool MoabThreadPool shows queued items that are not decreasing, MOAB is getting
too many requests to keep up.