Explanation | The managed bean (MBean) does not match the ObjectName class you specified. |
Action | Specify a broader ObjectName class pattern. |
Explanation | The new instrumentation level string cannot be saved to the ConfigService interface. |
Action | Resave the new instrumentation level string to the ConfigService interface. If the operation still fails, make sure your disk is not full. |
Explanation | Finding all the ObjectName classes on the specified server returned none. |
Action | Make sure the server specified has started and can respond to management commands. |
Explanation | Could not find the server managed bean (MBean) for a node. |
Action | The node agent must be running for the specified node. |
Explanation | A host name resolution problem occurred so the data collector could connect to the destination using the AdminClient application programming interface (API). |
Action | No action is required. If the source and destination are the same host, you can improve the performance by fixing the name resolution problem. |
Explanation | An error occurred trying to determine if the destination of the data collector was the local java virtual machine (JVM). Defaulting to a not local scenario still works. |
Action | Use the AdminClient application programming interface (API) to communicate with the destination host because it could not be verified that the destination was the local host. |
Explanation | The ConfigService interface could not find the PMIService AdminConfig object. |
Action | You must connect to a deployment manager instead of to an application server. |
Explanation | The ConfigService interface could not find the configuration ObjectName node. |
Action | You must connect to a deployment manager instead of to an application server. |
Explanation | The ConfigService interface could not find the configuration ObjectName server. |
Action | You must connect to a deployment manager instead of to an application server. |
Explanation | The server could not find the Perf managed bean (MBean). |
Action | You must enable the Performance Monitoring Infrastructure (PMI) service in the administrative console and restart the server. |
Explanation | The connection to the ConfigService interface failed. The data collector cannot access the ConfigService interface. But Performance Monitoring Infrastructure (PMI) data will be available. |
Action | You must connect to a deployment manager instead of to an application server. |
Explanation | The AdminClient application programming interface (API) could not connect to the server you specified. |
Action | The server specified must be running. If it isn't, start it. If it is, check that there are operational JMXConnectors. |
Explanation | The connection to the deployment manager is not being made because you are running in an application server and that configuration is not supported. |
Action | Use data collector from a client or directly in the deployment manager. |
Explanation | The managed bean (MBean) Factory failed to start the TivoliPerfEngine MBean that is needed by the Tivoli Performance Viewer (TPV). |
Action | This error is unexpected. The cause is not immediately known. Restart the application server and try again. If the problem persists, inspect the failure data that was generated during the failure. |
Explanation | The managed bean (MBean) Factory failed to start the TivoliPerfAdvisor MBean that is needed by the Tivoli Performance Advisor (TPA). |
Action | This error is unexpected. The cause is not immediately known. Restart the application server and try again. If the problem persists, inspect the failure data that was generated during the failure. |