Telemetry (AMQCO and AMQHT) messages
Reference information to help you identify and interpret the AMQCO and AMQHT messages for MQ Telemetry.
- AMQCO1001E
- MQXR service unexpectedly caught communications exception=<insert_0>(Exception).
- Explanation
- An exception was caught by the Communications Manager and it was not able to take a reasonable action in response to the exception.
- User action
- Investigate and resolve the cause of the underlying exception.
- AMQCO1002E
- A selection key=<insert_0> was found in an unexpected state.
- Explanation
- A selection key was found in a state that was not expected.
- User action
- Contact your IBM support center.
- AMQCO1003E
- Connection=<insert_0>(Connection) has insufficient data available to satisfy a get request.
- Explanation
- The application tried to read more data than is immediately available. After the application has processed the information available to it, it should release control and wait to be called again when more data is available.
- User action
- Change the application to handle this exception, or use Connection.available() before the get() method is called in order to determine if the get() will succeed.
- AMQCO1004E
- Connection Close error: <insert_0>.
- Explanation
- An error occurred when a connection was closed. The session might not have completed normally.
- User action
- Check that the session completed normally.
- AMQCO1005E
- SSL key repository file invalid or not found for channel ''<insert_1>''. The following exception was thrown: <insert_0>
- Explanation
- The SSL key repository file specified for the channel is not valid.
- User action
- Check the validity of the specified SSL key repository file.
- AMQCO1006I
- Channel ''<insert_0>'' has stopped.
- Explanation
- The channel has stopped. No further communication with clients will occur on this channel.
- User action
- No action is required.
- AMQCO1007E
- Connection ''<insert_0>'' did not send or receive data for ''<insert_1>'' milliseconds and has been closed.
- Explanation
- The application set the idle timer on the connection to <insert_1> milliseconds, but did not send or receive any data within this time, so the connection was closed.
- User action
- Determine why the connection did not send or receive data and if appropriate set the idleTimer to a longer value.
- AMQCO1008E
- An SSL Handshake error occurred when a client at ''<insert_1>'' attempted to connect to channel ''<insert_0>'': <insert_2>.
- Explanation
- An error occurred when performing an SSL handshake with a client application. This is often because the client is presenting certificates that the MQXR service does not trust.
- User action
- Use the information in the exception to diagnose and fix the problem.
- AMQCO1009E
- An invalid keystore name=''<insert_1>'' was specified.
- Explanation
- The keystore name or the pass phrase specified is not valid.
- User action
- Specify a valid keystore file name and password.
- AMQCO1010E
- An SSL Exception occurred when a client at ''<insert_1>'' attempted to connect to channel ''<insert_0>'': <insert_2>.
- Explanation
- An error occurred when performing an SSL operation with a client application.
- User action
- Use the information in the exception to diagnose and fix the problem.
- AMQCO2001E
- An error (probe: <insert_0>) occurred and a Failure Data Capture (FDC) file has been written.
- Explanation
- A problem was detected and a FDC file was written to aid diagnostics.
- User action
- Look at the FDC file and attempt to resolve the problem. If the problem cannot be resolved, contact your IBM support center.
- AMQCO2002I
- Trace is disabled.
- Explanation
- Tracing the MQXR Service (used in order to diagnose problems) is not currently running.
- User action
- No action is required.
- AMQCO2003I
- Trace is enabled.
- Explanation
- Tracing the MQXR Service (used in order to diagnose problems) is currently running.
- User action
- No action is required.
- AMQCO2004I
- ''<insert_0>'' instances of message ''<insert_1>'' were suppressed.
- Explanation
- The number <insert_0> of message identifier ''<insert_1>'' were suppressed from the log since the last message with this identifier was written.
- User action
- No additional action is required beyond that for the suppressed message.
- AMQCO9999E
- <insert_0>
- Explanation
- If the message does not give sufficient information, check previous messages for further help.
- User action
- See previous messages for further information.
- AMQHT1001E
- Invalid text=<insert_0>(String) was found in an HTTP request or response.
- Explanation
- An HTTP request or response contained unexpected data not described in "https://www.w3.org/Protocols/".
- User action
- Check that the originator or source of the HTTP request or response is producing valid requests or responses.
- AMQHT1002E
- HTTP header text=<insert_0>(String) was invalid.
- Explanation
- An HTTP request or response contained unexpected text.
- User action
- Check that the originator or source of the HTTP request or response is producing valid requests or responses.
- AMQHT1003E
- Invalid text at location=<insert_0> in string=<insert_1>(String).
- Explanation
- A Java Script Object Notation (JSON) string contained unexpected data not described in "https://www.json.org/".
- User action
- Check that the originator or JSON is producing valid data.
- AMQHT2001E
- WebSocket Close, status code= <insert_0>
- Explanation
- The websocket was closed by the remote end.
- User action
- Examine the Websocket status code and determine why the Websocket was closed if this was not expected.
- AMQHT9999E
- <insert_0>
- Explanation
- If the message does not give sufficient information, check previous messages for further help.
- User action
- See previous messages for further information.