Explanation | The WebSphere Java Management Extensions REST client encountered an error while preparing a request for the server |
Action | If you experience problems using the WebSphere Java Management Extensions REST client and observe this message, please contact IBM support. |
Explanation | The WebSphere Java Management Extensions REST client was unable to process a response from the server |
Action | If you experience problems using the WebSphere Java Management Extensions REST client and observe this message, please contact IBM support. |
Explanation | The WebSphere Java Management Extensions REST client received an unexpected response code from the server |
Action | If you experience problems using the WebSphere Java Management Extensions REST client and observe this message, please contact IBM support. |
Explanation | The server raised an exception handling the client request, but the client could not parse a Throwable object from the server error stream. The class of the Throwable object may not be available to the client. |
Action | Examine the cause of this exception and contact IBM support if you are unable to resolve the problem. |
Explanation | The connection to the server or was closed or has failed. |
Action | Check that the REST connector feature is enabled on the server and obtain a new connection to the server. |
Explanation | The client may have out-of-date information or the REST connector feature on the server may have been disabled. |
Action | Check that the REST connector feature is enabled on the server and obtain a new connection to the server. If the problem persists, please contact IBM support. |
Explanation | The class name argument must not be null. |
Action | Provide a non-null class name when calling the method. |
Explanation | The attribute name argument must not be null. |
Action | Provide a non-null attribute name when calling the method. |
Explanation | The argument containing an array of attribute names must not be null. |
Action | Provide a non-null array of attribute names when calling the method. |
Explanation | The Attribute argument must not be null. |
Action | Provide a non-null Attribute when calling the method. |
Explanation | The AttributeList argument must not be null. |
Action | Provide a non-null AttributeList when calling the method. |
Explanation | The ObjectName argument must not be null. |
Action | Provide a non-null ObjectName when calling the method. |
Explanation | The exception wraps a Throwable object returned from the server that is not normally expected for this operation. |
Action | If you experience problems using the WebSphere Java Management Extensions REST client and observe this message, please contact IBM support. |
Explanation | The credentials provided when obtaining the connection were incorrect. The user may not exist or may not have authority to access the server, or the password may be incorrect. |
Action | Correct the user name or password, then obtain a new connection. |
Explanation | The ObjectName argument is a pattern but the method requires an ObjectName matching exactly one MBean. |
Action | Provide an ObjectName argument without wildcards that will match exactly one MBean. |
Explanation | The operation requires a registered MBean, but no MBean with the given ObjectName was registered. |
Action | Ensure the MBean is registered before attempting to perform management operations on it. |
Explanation | The MBean does not provide an attribute of the given name. |
Action | Obtain the MBean information to confirm which attributes the MBean provides. |
Explanation | The MBean does not provide an operation of the given name. |
Action | Obtain the MBean information to confirm which operations the MBean provides. |
Explanation | The NotificationListener was not added or has already been removed and is not currently registered to receive notifications from the given MBean. |
Action | Make sure the calling code tracks which NotificationListeners have been added and removed or catch and handle the exception. |
Explanation | A notification could not be delivered to one or more NotificationListeners because a registered NotificationListener was not found or there was an exception during delivery of the notification. |
Action | If the notification should have been delivered to a registered NotificationListener, check the logs for exceptions and contact IBM support if you are unable to resolve the problem. |
Explanation | The server became unavailable and did not become available again within the configured maximum time allowable. |
Action | Check the network connection and ensure that the server is running with the REST connector feature enabled. |
Explanation | The server has become unavailable, but the client will attempt to restore the connection for the duration of the configured maximum time allowable. |
Action | If the server is intentionally restarting, no action is required. Otherwise, check the network connection and ensure that the server is running with the REST connector feature enabled. |
Explanation | The connection to the server was temporarily lost but has been restored successfully. Exceptions were encountered while adding NotificationListeners, so some notifications may not be received. |
Action | Check the exceptions included with the notification and re-register NotificationListeners after correcting the problems. |
Explanation | The connection to the server was temporarily lost but has been restored successfully. Any registered NotificationListeners will continue to receive notifications. |
Action | None |
Explanation | The value for the parameter 'serviceURL' cannot be null. |
Action | Re-connect to the JMX REST Connector using a non-null JMXServiceURL value. |
Explanation | The specified endpoint value is not valid. |
Action | Re-connect to the JMX REST Connector using a valid endpoint value that is of type String and has the format "host:port". |
Explanation | None of the specified endpoints were available during the JMX REST Connector's initialization. |
Action | Re-connect to the JMX REST Connector using at least 1 available endpoint. |