AMQXR Messages
- AMQCO1001E
- MQXR service unexpectedly caught communications exception={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={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={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: {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 ''{1}''. The following exception was thrown: {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 ''{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 ''{0}'' did not send or receive data for ''{1}'' milliseconds and has been closed.
- Explanation
- The application set the idle timer on the connection to {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 ''{1}'' attempted to connect to channel ''{0}'': {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 Key Store name=''{1}'' was specified.
- Explanation
- The key store name or the pass phrase specified is not valid.
- User action
- Specify a valid key store file name and password.
- AMQCO1010E
- An SSL Exception occurred when a client at ''{1}'' attempted to connect to channel ''{0}'': {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: {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
- ''{0}'' instances of message ''{1}'' were suppressed.
- Explanation
- The number {0} of message identifier ''{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
- {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={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/pub/WWW/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={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={0} in string={1}(String).
- Explanation
- A Java Script Object Notation (JSON) string contained unexpected data not described in "http://www.json.org/".
- User action
- Check that the originator or JSON is producing valid data.
- AMQHT2001E
- WebSocket Close, status code= {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
- {0}
- Explanation
- If the message does not give sufficient information, check previous messages for further help.
- User action
- See previous messages for further information.
- AMQXR0001I
- Client {0} disconnected normally.
- Explanation
- An MQTT disconnect flow was received and processed.
- User action
- None.
- AMQXR0002E
- On channel {2}, a throwable {1} resulted when the MQXR service received a message from an MQTT client {0}.
- Explanation
- Bad data was received from a network connection and could not be processed, the connection is closed by the server.
- User action
- Determine why the client sent the uninterpretable data.
- AMQXR0003I
- MQXR JAAS {0} : {1}.
- Explanation
- The JAAS callback in the MQXR service requested that the message is displayed to the user.
- User action
- Determine the cause of the security problem described in the text of the message issued by JAAS.
- AMQXR0004E
- MQSeries verb={0}(String) returned cc={1}(int) {2} rc={3}(int) {4}.
- Explanation
- A WebSphere MQ verb returned an unexpected reason and completion code.
- User action
- Look up the reason code to determine what caused the error.
- AMQXR0005I
- Running {0} version {1}.
- Explanation
- The command is running.
- User action
- None.
- AMQXR0006E
- Invalid argument {0} Usage: runMQXRService -m <queueManagerName> -d <Qmgr Data Directory> -g <MQ Global Data directory>
- Explanation
- The runMQXRService command arguments are incorrect.
- User action
- Correct the command.
- AMQXR0007E
- Invalid argument {0} Usage: endMQXRService -m <queueManagerName> -d <Qmgr Data Directory> -g <MQ Global Data directory>
- Explanation
- The endMQXRService command arguments are incorrect.
- User action
- Correct the command.
- AMQXR0008E
- Exception during start of MQXR service: {0}
- Explanation
- The MQXR service was starting but encountered a problem. Previous errors or FDCs will provide more detail.
- User action
- Use previous errors or FDCs to diagnose and address the problem then restart the MQXR service.
- AMQXR0009E
- Exception during shutdown of MQXR service: {0}
- Explanation
- The MQXR service was shutting down but encountered a problem. Previous errors or FDCs will provide more detail.
- User action
- Use previous errors or FDCs to diagnose and address the problem.
- AMQXR0010E
- An invalid ClientIdentifier {0} was received from ''{1}'' in an MQTT CONNECT packet on channel {2}.
- Explanation
- The MQXR service received a ClientIdentifier that is not valid because it contains too few, or too many characters, or the characters are not valid in a queue manager name.
- User action
- Change the ClientIdentifier to use valid characters.
- AMQXR0011E
- An error occurred during a publish on topic ''{3}'' from ClientIdentifier ''{0}'' UserName ''{1}'' on channel ''{2}''. A reason code of ''{5}'' ''{6}'' was received during an ''{4}'' operation.
- Explanation
- The publication from the client was not able to be completed
- User action
- Using the reason code, diagnose the cause of the problem, alter the configuration (of the client or the server as appropriate) and then retry the publish.
- AMQXR0012E
- An error occurred whilst subscribing on topic(s) ''{3}'' for ClientIdentifier ''{0}'' userNamer ''{1}''on channel ''{2}''. A reason code of ''{5}'' ''{6}'' was received during an ''{4}'' operation.
- Explanation
- The subscription from the client was not able to be completed
- User action
- Using the reason code, diagnose the cause of the problem, alter the configuration (of the client or the server as appropriate) and then reconnect the client and retry the subscription.
- AMQXR0013E
- Error starting channel ''{0}'' (on host: ''{1}'' and port ''{2}''). The exception was ''{3}''.
- Explanation
- The service was unable to listen for connections on the specified port
- User action
- Use the exception to diagnose and rectify the problem then restart the affected channel.
- AMQXR0014E
- Error starting channel ''{0}''. See earlier errors or FDCs for more details.
- Explanation
- The service was unable to listen for connections on the specified port because of problems that have been reported in earlier errors or FDCs.
- User action
- Use the preceding errors or FDCs to diagnose and rectify the problem then restart the affected channel.
- AMQXR0015I
- MQXR Service started successfully ({0} channels running, {1} channels stopped)
- Explanation
- The MQXR service has completed the processing that occurs on startup
- User action
- No action is required.
- AMQXR0016I
- Channel ''{0}'' has started
- Explanation
- This channel is now available for client connections
- User action
- No action is required
- AMQXR0017I
- A new channel (called ''{0}'') has been created
- Explanation
- In response to a request from a user, a new channel has been created
- User action
- No action is required
- AMQXR0018I
- Channel ''{0}'' has been altered
- Explanation
- In response to a request from a user, some settings on the channel were changed. Some settings do not take effect until the channel is restarted.
- User action
- No action is required
- AMQXR0019I
- Channel ''{0}'' has been deleted
- Explanation
- In response to a request from a user, a new channel has been deleted
- User action
- No action is required
- AMQXR0020I
- Channel ''{0}'' has been purged
- Explanation
- Clients have been disconnected from this channel and state associated with them has been removed
- User action
- No action is required
- AMQXR0021W
- Client ''{0}'' at network address ''{1}'' disconnected abnormally with exception ''{2}''.
- Explanation
- An MQTT client was disconnected from the network for the reason shown by the exception.
- User action
- Look into the exception cause to determine if action is required.
- AMQXR0022I
- Client ''{0}'' previously connected at network address ''{1}'' now connected at ''{2}''.
- Explanation
- A new connection has been made for the client taking over from an existing one.
- User action
- None, if this was intentional.
- AMQXR0023I
- Unsupported MQTT protocol version on channel {1}, the exception {0} was thrown.
- Explanation
- An MQTT client attempted to connect using an unsupported protocol version, the connection is closed by the server.
- User action
- Reconfigure the client to use a supported protocol version.
- AMQXR0024I
- A Telemetry Daemon for devices attempted to connect using its private protocol on channel {1}, the exception {0} was thrown.
- Explanation
- The Telemetry daemon for devices has a private protocol for communication. This protocol is not supported and the connection has been closed by the server.
- User action
- No user action is required, the daemon should reconnect with a supported protocol. To remove this message, reconfigure the Telemetry daemon for devices to not use the private protocol for this connection.
- AMQXR0030W
- Invalid Will Message from ClientIdentifier ''{0}''
- Explanation
- The Will Message in the Connect packet is malformed, the client connection is closed by the server.
- User action
- Check the client application and make sure the will message has a non zero length topic name, and a valid Qos.
- AMQXR1001E
- MQTTV3Exception message={0}(String).
- Explanation
- An instance of com.ibm.mqttv3.internal.MQTTException has been caught and wrapped.
- User action
- Contact your IBM support center.
- AMQXR1002E
- MQTTV5Exception message={0}(String).
- Explanation
- An instance of com.ibm.mqtt.encoding.internal.MQTTException has been caught and wrapped.
- User action
- Contact your IBM support center.
- AMQXR1003E
- An invalid message type={0}(byte) was received.
- Explanation
- An invalid MQTT message type was received. The connection is disconnected.
- User action
- The client connected to the MQXR service is sending invalid MQTT messages. \ Find out what client has connected to the MQXR service and what data it has sent. Contact the provider of the client code. If you are using a client provided in the WebSphere MQ installation, \ contact your IBM support center.
- AMQXR1004E
- An invalid message version={0}(byte) subVersion={1}(byte) was received.
- Explanation
- An invalid MQTT message version was received. The connection is disconnected.
- User action
- The client connected to the MQXR service is sending invalid MQTT messages. Find out what client has connected to the MQXR service and what data it has sent. Contact the provider of the client code. If you are using a client provided in the WebSphere MQ installation, contact your IBM support center.
- AMQXR1005E
- An invalid message message={0}(Hex) was received.
- Explanation
- An invalid MQTT message was received. The connection is disconnected.
- User action
- The client connected to the MQXR service is sending invalid MQTT messages. Find out what client has connected to the MQXR service and what data it has sent. Contact the provider of the client code. If you are using a client provided in the WebSphere MQ installation, contact your IBM support center.
- AMQXR10006E
- An MQTT message with an invalid MultiByteLength={0}(long) was received.
- Explanation
- An invalid MQTT message containing an invalid multi-byte length was received. The connection is disconnected.
- User action
- The MQTT client application might have sent incorrect data, which is interpreted as an incorrect length. Check your MQTT client application, and verify that it is sending correct data. Contact the provider of the client code. If you are using a client provided in the WebSphere MQ installation, contact your IBM support center.
- AMQXR1007E
- An invalid Attribute type={0}(int) was found.
- Explanation
- An invalid MQTT attribute was found processing of this message is abandoned and the connection closed.
- User action
- Gather diagnostics and contact your IBM support center.
- AMQXR1008E
- An invalid mapped message was detected because of {0}(String).
- Explanation
- An invalid Mapped message was found, it cannot be processed.
- User action
- Determine where the message came from and correct the messages so that they are not mapped messages or are created with the correct format.
- AMQXR1009E
- An invalid WebSocket message was detected because of {0}(String).
- Explanation
- An invalid WebSocket message was found, it cannot be processed.
- User action
- Determine where the message came from and correct the messages so that they are correctly formed.
- AMQXR1010E
- An invalid message qos={0}(int) was received.
- Explanation
- An invalid MQTT qos was received.
- User action
- The client connected to the MQXR service is sending invalid MQTT messages. Find out what client has connected to the MQXR service and what data it has sent. Contact the provider of the client code. If you are using a client provided in the WebSphere MQ installation, contact your IBM support center.
- AMQXR2001E
- The command to end the MQXR service failed connecting to queue manager {0}. Exception: {1}
- Explanation
- The administrative layer could not connect to the queue manager.
- User action
- If the queue manager is no longer running, no action is required. If the queue manager is still running, check why the administrative layer is unable to connect.
- AMQXR2002E
- The command to end the MQXR service failed opening queue {0}. Exception: {1}
- Explanation
- The administrative layer could not open the queue that is required to send a request end the MQXR service.
- User action
- Determine why the queue could not be opened and retry stopping the service.
- AMQXR2003E
- The command to end the MQXR service failed: Failed Operation: {0} Exception ({1}): {2}
- Explanation
- The administrative layer failed to put or get a message that is required to stop the MQXR service.
- User action
- Correct the problem and then try stopping the service again.
- AMQXR2004E
- An error occurred while stopping the MQXR service. Completion Code: {0} Reason: {1}
- Explanation
- An error occurred while the MQXR service was shutting down.
- User action
- Use the reason code to diagnose the problem.
- AMQXR2005E
- An error occurred while releasing queue manager resources. Object: {0} Exception: {1}
- Explanation
- While cleaning up resources the EndMQXRService command encountered a transient problem.
- User action
- None.
- AMQXR2010E
- The MQXR service could not access the file: {0}. Exception: {1}
- Explanation
- The file is invalid, has an invalid format, or incorrect permissions.
- User action
- Check the file permissions and ensure the file is valid.
- AMQXR2011I
- Property {0} value {1}
- Explanation
- The runMQXRService command has read a property with the assigned value.
- User action
- None.
- AMQXR2012E
- Invalid property key={0} value={1}
- Explanation
- The runMQXRService command read an incorrect properties file.
- User action
- Look at the property in error, correct it, and reissue the command.
- AMQXR2014E
- Failed to rename {0} to {1}
- Explanation
- The file could not be renamed
- User action
- Look at the permissions on the target file and directory and alter them if necessary
- AMQXR2013E
- Duplicate authentication methods specified for channel={0}, previous={1} duplicate={2}
- Explanation
- The runMQXRService command read a properties file that specifies two authentication methods, only one is allowed.
- User action
- Look at the properties file and locate the definition of the named channel. Correct the file to specify a single authentication method and restart the channel.
- AMQXR2014E
- The following exception was thrown during the starting of an MQXR channel, channelName = ''{0}'' : {1}
- Explanation
- An MQXR channel was starting up but encountered a problem. Previous errors or FDCs will provide more detail.
- User action
- Use earlier errors or FDCs to diagnose and address the problem then restart the MQXR channel.
- AMQXR2015E
- The following exception was thrown during the stopping of an MQXR channel, channelName = ''{0}'' : {1}
- Explanation
- An MQXR channel was stopping but encountered a problem. Previous errors or FDCs will provide more detail.
- User action
- Use earlier errors or FDCs to diagnose and address the problem then restart the MQXR channel.
- AMQXR2020E
- Client {0} attempted to unsubscribe from the topic ''{1}'' which it is not subscribed to.
- Explanation
- An MQTT client attempted to unsubscribe from a topic it is not subscribed to.
- User action
- Check that the application logic is correct, and check for earlier errors that could have caused the application to get into an inconsistent state.
- AMQXR2021E
- Client {0} attempted to unsubscribe from the queue ''{1}'' which it is not subscribed to.
- Explanation
- An MQTT client attempted to unsubscribe from a queue it is not subscribed to.
- User action
- Check that the application logic is correct, and check for earlier errors that could have caused the application to get into an inconsistent state.
- AMQXR2050E
- Unable to load JAAS config: {0}. The following exception occurred {1}
- Explanation
- The JAAS configuration tried to authenticate a user on a connection that was unable to load
- User action
- Check that the JAAS config selected by the channel exists in the jaas.config file and is valid.
- AMQXR2051E
- Login failed for ClientIdentifier {0} with exception {1}.
- Explanation
- The JAAS login failed with the exception shown.
- User action
- Check that the username and password sent by the client are correct.
- AMQXR2053E
- Error in a trace factory. The following exception occurred {1}
- Explanation
- There was a problem starting or stopping trace.
- User action
- Use the exception to diagnose and rectify the problem and then restart trace.
- AMQXR9999E
- {0}
- Explanation
- If the message does not give sufficient information, check previous messages for further help.
- User action
- See previous messages for further information.