After upgrading Websphere from release 7 to 8.5.5, some of the instances on one Server stopped reporting Frontend or Servlet metrics.
The following is the same on both systems:
Inspection of the Autoprobe logs showed that a difference in HTTPServletTracer class insertion. This is the tracer responsible for marking the Frontend and Servlet metrics in this application. HTTPServletTracer was inserted into the following classes in the working environments:
In the non-working environments, the tracer was inserted in just the following class where the Frontends were not being reported:
As each application executes correctly in the various environments, it is implied that the classes are not seen by the Agent. One reason for this could be that the classes had been cached. If this is the case, then clearing the cache resolves the problem
Websphere can use a class caching feature. If needed, clearing the cache by simply restarting the JVM will not remove cached classes. This can apply after an upgrade. Follow the procedure in this URL:
All Supported APM Releases.
The server must be stopped before clearing the caches and the process must be performed by the user which starts Websphere:
1. To clear the OSGi class cache:
For UNIX platforms, run the following script in each profile:
For Windows platforms, run the following script in each profile:
2. To clear the JVM's class cache (Windows, Linux and AIX only) :
For UNIX platforms, run the following script:
For Windows platforms, run the following script:
And also clear the following directory contents: