Telemetry (AMQCO) messages
- AMQCO1001E
- 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.
- Response
- 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.
- Response
- 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.
- Response
- 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
- <insert_0>.
- Explanation
- An error was produced when an connection was closed.
- Response
- The connection was closed but the session might not have completed normally.
- AMQCO1005E
- <insert_0>
- Explanation
- The SSL key repository file specified for the channel is invalid
- Response
- Check the validity of the specified SSL key repository file
- AMQCO1006I
- Channel <insert_0> has stopped
- Explanation
- The channel is stopped, no further communication with clients will occur on this channel
- Response
- No action is required
- AMQCO1007E
- Connection <insert_0> for client <insert_1> did not send or receive data for <insert_2> 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, the connection was closed.
- Response
- Determine why the connection did not send or receive data and if appropriate set the idleTimer to a longer value.
- AMQCO1008E
- <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 service does not trust.
- Response
- Use the information in the exception to diagnose and fix the problem.
- AMQCO1009E
- An invalid Key Store name=<insert_0> was specified.
- Explanation
- The key store name or the pass phrase specified is not valid.
- Response
- Specify a valid key store file name and password.
- AMQCO1010E
- <insert_2>.
- Explanation
- An error occurred when performing an SSL operation with a client application.
- Response
- Use the information in the exception to diagnose and fix the problem.
- AMQCO1011I
- The IBMJSSE2 provider was not found. Falling back to using a protocol supported by the SunJSSEProvider.
- Explanation
- A non-IBM JRE is being used which does not support the full suite of protocols.
- Response
- No action is required.
- AMQCO1012I
- Not authorized to access the command server queue <insert_0>. Checking command server availability is not possible.
- Explanation
- If the command server queue cannot be accessed then it is not possible to determine the state of the command server, and unpredictable behavior might result.
- Response
- Examine the queue manager logs to determine why the command server queue cannot be accessed. If the problem cannot be resolved, contact your IBM support center.
- AMQCO1013I
- command server is not running.
- Explanation
- The service requires the command server to be running to access the queue manager.
- Response
- Start the command server, then restart the service.
- AMQCO1014E
- Security provider <insert_0>, required for key store <insert_1>, is not installed.
- Explanation
- The JRE security configuration does not contain the required security provider.
- Response
- Ensure that the correct JRE is being used for the service and that its security environment has been configured correctly. Note that the default MQ installation JRE should already have the required security environment setup. If the problem cannot be resolved, contact your IBM support center.
- AMQCO1015E
- Problem obtaining security provider required for key store <insert_0>, reason <insert_1>
- Explanation
- The required key store provider implementation for the key store type is not available.
- Response
- Ensure that the correct JRE is being used for the service and that its security environment has been configured correctly. Note that the default MQ installation JRE should already have the required security environment setup. If the problem cannot be resolved, contact your IBM support center.
- AMQCO1016E
- Failed to load key store <insert_0>, reason <insert_1>
- Explanation
- The key store could not be loaded for the given reason.
- Response
- Check that the key store file content is valid. The reason given for the load failure should describe the particular problem. If the problem cannot be resolved, contact your IBM support center.
- AMQCO1017E
- An invalid key store stash file<insert_0> was specified.
- Explanation
- The key store stash file does not exist or is not accessible.
- Response
- Specify a valid key store stash file.
- AMQCO1018E
- Logout failed for ClientIdentifier <insert_0> with exception <insert_1>.
- Explanation
- The JAAS logout failed with the exception shown.
- Response
- Examine the reason for the logout failure and take any appropriate action.
- AMQCO1019E
- An error occurred while decrypting the passphrase for channel <insert_0>. The exception was <insert_1>.
- Explanation
- An error occurred while decrypting the passphrase for the channel.
- Response
- Verify that a valid key file is provided for the MQXR service and try updating the channel passphrase. The channel will then need to be attempted to be started again.
- AMQCO1020E
- An error occurred while encrypting the passphrase for channel <insert_0>. The exception was <insert_1>.
- Explanation
- An error occurred while encrypting the passphrase for the channel.
- Response
- Verify that a valid key file is provided for the MQXR service and try updating the channel passphrase. The channel will then need to be attempted to be started again.
- AMQCO1021E
- An invalid eye catcher <insert_0> found in the passphrase for channel <insert_1>.
- Explanation
- Encrypted passphrase contains an invalid eye catcher.
- Response
- Ensure the passphrase is encrypted as suggested in the IBM documentation. It maybe necessary to update the passphrase for the channel. If the problem cannot be resolved contact your IBM support center.
- AMQCO1022E
- An unknown algorithm value <insert_0> was found in the passphrase for channel <insert_1>.
- Explanation
- Encrypted passphrase contains an invalid or unsupported algorithm.
- Response
- Ensure the passphrase is encrypted as suggested in the IBM documentation. It maybe necessary to update the passphrase for the channel. If the problem cannot be resolved contact your IBM support center.
- AMQCO1023E
- Invalid encrypted passphrase format for channel <insert_0>.
- Explanation
- The passphrase is not in the expected encrypted format.
- Response
- Verify that a valid key file is provided for the MQXR service and change the passphrase of channel. Then attempt to start the channel.
- AMQCO1024E
- Queue manager is configured with keystore <insert_0> which has an unsupported keystore type <insert_1> for an AMQP channel.
- Explanation
- The keystore type is not supported for an AMQP channel.
- Response
- Configure the queue manager with a PKCS12 keystore if you want to use AMQP channels.
- AMQCO1025E
- The channel could not be started because the SSLKEYP attribute has not been set for keystore <insert_0>.
- Explanation
- The passphrase required for accessing the keystore has not been provided.
- Response
- Specify the passphrase for the TLS key repository using the SSLKEYP parameter of the channel definition.
- AMQCO9999E
- <insert_0>