Missing AutoProbe metrics after upgrading the Java Agent to monitor WebSphere.

Document ID : KB000009202
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

The customer had upgraded the agent.

It was reporting data to the Enterprise Manager but the key AutoProbe metrics like Frontends, Backends, EJBs were missing.

There were no indications of AutoProbe failure and some AutoProbe metrics were visible.

Environment:
WebSphere running in z/Linux
Cause:

IBM WebSphere uses a class caching facility to improve performance of its application.

Because we are performing bytecode instrumentation, traces of our own code are present in the cached versions of the cache.

When there are upgrades to the agent, there can be differences in the cached code and the latest code of our agent.

Resolution:

For all agent upgrades when monitoring WebSphere, you should clear the class cache before running with the new agent version.

For example

For UNIX and z/OS platforms, run the following script:
<WebSphere_HOME>/bin/clearClassCache.sh

Additional Information:

Link to IBM documentation on clearing the WebSphere class caches

http://www-01.ibm.com/support/docview.wss?uid=swg21607887