On WebSphere, the following error messages and issues can occur when you are using Detailed Diagnostics.
| Top 10 EJB\s is not working
Explanation:
The Average Method Response Time attribute on which sorting is done for Detailed Diagnostics has a high impact on WebSphere\ 5.0 and a low impact on WebSphere 4.0.x Application Server.
User Response:
Set the impact level for beanModule to High on WebSphere 5.0 and low or above on a WebSphere 4.0.x Application Server. |
| Top Servlets and JSPs is not working
Explanation:
The Average Response Time attribute on which sorting is done for the Top 10 Servlet has a medium impact on WebSphere 5.0 and WebSphere 4.0.x Application Servers.
User Response:
For Detailed Diagnostics to function, set the impact level for the webAppModule to medium or above on WebSphere 5.0 and WebSphere 4.0.x Application Servers. |
| Detailed Diagnostics fails to generate the expected output for Top 10 Servlets
Explanation:
This message indicates that the application server is not running, Performance Monitoring for the webAppModule is not enabled, the impact is too low on WebSphere, or the Performance Servlet URL is incorrect.
User Response:
Invoke the Performance Servlet from a web browser and ensure that the following settings are correct: - Application Server is running.
- Performance Monitoring for the webAppModule is enabled.
- Impact is set to Medium or above on the WebSphere 4.0.x or WebSphere 5.0 Application Server.
- Performance Servlet default URL is http://appServerIP or aliasName:Port/wasPerfTool/servlet/perfservlet.
|
| Data Collection for Average Response Time attribute has not been enabled on the WebSphere Application Server--error message
Explanation:
The Performance Monitoring for the Average Response Time attribute is not enabled on the WebSphere Application Server.
User Response:
Enable Performance Monitoring for the Average Response Time attribute. |
| Getting the Top 10 Servlets / JSP's for the Application Server failed--error message
Explanation:
The Application Server is not running, Performance Monitoring is not enabled on the Application Server, or the Performance Servlet timed out.
User Response:
Start the Application Server and enable the Performance Monitor on the Application Server, as needed. You can change the timeout property value in the pronet.conf file. |