Explanation | There is no MBean that matches the ObjectName specified. |
Action | Try specifying a broader ObjectName pattern. |
Explanation | The attempt to save the new instrumentation level string to the WebSphere Config Service failed. |
Action | Try the operation again. If it still fails, make sure your disk is not full. |
Explanation | Finding all the ObjectName's on the specified server returned none. |
Action | Make sure the server specified has started and can respond to management commands. |
Explanation | An attempt to get the Server MBean for a node failed. |
Action | You should make sure the node agent is running for the specified node. |
Explanation | A hostname resolution problem occurred so the Collector will connect to the destination using the AdminClient. |
Action | None required. If the source and destination are the same host, performance can be improved by fixing the name resolution problem. |
Explanation | An error occurred trying to determine if the destination of the Collector was local to the current JVM. Defaulting to a not local scenario still works. |
Action | None required. The AdminClient will be used to communicate with the destination host since it could not be verified that the destination was the local host. |
Explanation | The PMIService config ObjectName could not be found by the config service. |
Action | Make sure you are connected to the Deployment Manager instead of to an Application Server. |
Explanation | The node config ObjectName could not be found by the config service. |
Action | Make sure you are connected to the Deployment Manager instead of to an Application Server. |
Explanation | The server config ObjectName could not be found by the config service. |
Action | Make sure you are connected to the Deployment Manager instead of to an Application Server. |
Explanation | The perf MBean could not be found for the server. |
Action | Make sure you enabled the PMI Service in the admin console and restarted the server. |
Explanation | The connection to the ConfigService failed. Attempts to access it by the Collector will fail. PMI data will still be available. |
Action | Make sure you are connected to the Deployment Manager instead of to an Application Server. |
Explanation | The AdminClient connection to the server specified could not be made. |
Action | Make sure the server specified is 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 App Server and that configuration is not supported. |
Action | Use the DataCollector from a client or directly in the Deployment Manager. |
Explanation | The MBean Factory failed to start the TivoliPerfEngine MBean needed by the Tivoli Performance Viewer. |
Action | Inspect the failure data that was generated due to this failure. |
Explanation | The MBean Factory failed to start the TivoliPerfAdvisor MBean needed by the Tivoli Performance Advisor. |
Action | Inspect the failure data that was generated due to this failure. |