Error Code | Description |
ADA.0600.1020 | Get completed with conditionCode=conditionCode, reasonCode=reasonCode. |
ExplanationThis information message is generated to provide additional debug information when a Get service returns a non-zero reason code. | |
ActionRefer to the WebSphere MQ manuals to determine the meaning of the reason code. | |
ADA.0600.1030 | Put completed with conditionCode=conditionCode, reasonCode=reasonCode. |
ExplanationThis information message is generated to provide additional debug information when a Put service returns a non-zero reason code. | |
ActionRefer to the WebSphere MQ manuals to determine the meaning of the reason code. | |
ADA.0600.1040 | Peek completed with conditionCode=conditionCode, reasonCode=reasonCode. |
ExplanationThis information message is generated to provide additional debug information when a Peek service returns a non-zero reason code. | |
ActionRefer to the WebSphere MQ manuals to determine the meaning of the reason code. | |
ADA.0600.1050 | Request/Reply completed with conditionCode=conditionCode, reasonCode=reasonCode. |
ExplanationThis information message is generated to provide additional debug information when a Request/Reply service returns a non-zero reason code. | |
ActionRefer to the WebSphere MQ manuals to determine the meaning of the reason code. | |
ADA.0600.1051 | Request/Reply requires a valid, non-null value in theMQMDPropertyName property of the msgHeader. |
ExplanationThe Request/Reply service was invoked with a null value in the specified msgHeader property. This property must contain a non-null value. | |
ActionSpecify a non-null value for this property. | |
ADA.0600.1052 | Request/Reply service requires a non-transactional connection. |
ExplanationThe Request/Reply service was invoked with a transactional connection. The Request/Reply service requires a non-transactional connection. | |
ActionModify the configuration of this service to use a non-transactional connection. | |
ADA.0600.1055 | Exception caught action: exceptionMessage. |
ExplanationA Java Exception has been caught. | |
ActionDetermine the cause of the exception and correct the problem. If necessary, provide this information to a Software AG Global Support representative. | |
ADA.0600.2055 | Exception caught: exceptionMessage. |
ExplanationA Java Exception has been caught. | |
ActionDetermine the cause of the exception and correct the problem. If necessary, provide this information to a Software AG Global Support representative. | |
ADA.0600.2062 | PCFQuery could not connect to the Queue Manager queueManagerName - reasoncode=reasonCode. |
ExplanationThe PCFQuery class could not connect to the specified queue manager. The PCFQuery class is used when retrieving the list of available queues on a queue manager. | |
ActionDetermine the cause of the exception and correct the problem. If necessary, provide this information to a Software AG Global Support representative. | |
ADA.0600.2063 | PCFQuery sent to queueManagerName failed, compcode=conditionCode, reasoncode=reasonCode. |
ExplanationThe PCFQuery class sent a command to the specified Queue Manager, but it failed. The PCFQuery class is used when retrieving the list of available queues on a Queue Manager. | |
ActionRefer to the WebSphere MQ manuals to determine the meaning of the reason code. | |
ADA.0600.3020 | MsgBody must be a byte[], a String, or a Serializable Object. Found dataType. |
ExplanationThe msgBody property could not be set because it contained an invalid object. The supported data types are byte array, string, or a serializable object. | |
ActionProvide a msgBody property that contains a valid data type. | |
ADA.0600.3032 | Queue Manager queueManagerName has disconnected, waiting milliseconds milliseconds before reconnecting. |
ExplanationA fatal Exception has been caught, and the connection to the specified Queue Manager has been lost. The adapter will attempt to reconnect in milliseconds milliseconds. | |
ActionLook for other error messages in the server log to determine why the connection to the queue manager was lost. | |
ADA.0600.3033 | Connection to Queue Manager queueManagerName could not be initialized; conditionCode and reasonCode. |
ExplanationThe adapter could not connect to the specified queue manager. | |
ActionRefer to the WebSphere MQ manuals to determine the meaning of the reason code. | |
ADA.0600.3034 | Queue queueName could not be opened for Input/Output/Inquire; exceptionMessage. |
ExplanationThe specified queue could not be opened successfully. | |
ActionDetermine the cause of the exception and correct the problem. If necessary, provide this information to a Software AG Global Support representative. | |
ADA.0600.3035 | Unable to put message to queue queueName on queueManagerName; condition code is conditionCode, reason code is reasonCode. |
ExplanationThe adapter failed to put a message to the specified queue on the specified queue manager. | |
ActionRefer to the WebSphere MQ manuals to determine the meaning of the reason code. | |
ADA.0600.3036 | Unable to get message from queue queueName on queueManagerName; condition code is conditionCode, reasonCode is reasonCode. |
ExplanationThe adapter failed to get a message from the specified queue on the specified Queue Manager. | |
ActionRefer to the WebSphere MQ manuals to determine the meaning of the reason code. | |
ADA.0600.3037 | Unable to peek message on queue queueName on queueManagerName; conditionCode is conditionCode,reasonCode is reasonCode. |
ExplanationThe adapter failed to peek at a message on the specified queue on the specified Queue Manager. | |
ActionRefer to the WebSphere MQ manuals to determine the meaning of the reason code. | |
ADA.0600.3038 | Unable to commit message(s) on queue queueName on queueManagerName; conditionCode=conditionCode, reasonCode=reasonCode. |
ExplanationThe adapter failed to commit an active transaction on the specified queue on the specified queue manager. | |
ActionRefer to the WebSphere MQ manuals to determine the meaning of the reason code. | |
ADA.0600.3039 | Unable to rollback message(s) on a queue queueName on queueManagerName; conditionCode is conditionCode, reasonCode is reasonCode. |
ExplanationThe adapter failed to rollback an active transaction on the specified queue using the Queue Manager. | |
ActionRefer to the WebSphere MQ manuals to determine the meaning of the reason Code. | |
ADA.0600.3040 | Service serviceName moved a message to the DeadLetterQueue deadLetterQueueName. |
ExplanationOne of the following errors occurred: 1) a message could not be delivered to a specified queue, or 2) a message was received whose Backout Count property exceeded the Backout Threshold for this service. | |
ActionLook for other error messages in the server log to determine the cause of the problem. | |
ADA.0600.3041 | Failure attempting to move message to the DeadLetterQueue deadLetterQueueName. Error: errorMessage. |
ExplanationOne of the following errors occurred: 1) a message could not be delivered to the specified dead letter queue, or 2) A message was received whose Backout Count property exceeded the Backout Threshold for this service. However, the adapter could not move the message to the dead letter queue, due to another error. | |
ActionLook for other error messages in the server log to determine the cause of the initial problem. Note that in watt.WmMQAdapter.includeDataInError3041, you can set whether the 3041 message should include a hex dump of the payload data of the message that could not be written to the dead letter queue in the server log. Valid values are (true|false). The default is false (do not include the hex dump). | |
ADA.0600.3044 | A warning was received while putting a message to queue queueName: MQExceptionMessage. |
ExplanationAn MQException with condition code = WARNING was caught while putting a message to the specified queue. | |
ActionLook for other error messages in the server log to determine the cause of the initial problem. | |
ADA.0600.3045 | Unable to inquire the queue manager qmgr name; condition code is mq condition code, reason code is mq reason code. |
ExplanationUnable to inquire the queue manager. | |
ActionLook for the reason code returned by WebSphere MQ and take corrective action mentioned in the WebSphere MQ documentation. | |
ADA.0600.3046 | Unable to inquire the queue name on qmgr name; condition code is mq condition code, reason code is mq reason code. |
ExplanationUnable to inquire the queue. | |
ActionLook for the reason code returned by WebSphere MQ and take the corrective action mentioned in the WebSphere MQ documentation. | |
ADA.0600.3099 | The message received by Listener listenerName was not processed by any Notification. |
ExplanationA message was received by the specified listener, but none of the associated Notifications support the message type. | |
ActionLook for other error messages in the server log to determine why the notifications do not support the message. | |
ADA.0600.4011 | Exception caught while loading exit exitName. (exceptionType)exit Name. |
ExplanationError occurred when WebSphere MQ Adapter attempted to load the specified exit class. | |
ActionDetermine the cause of the exception and correct the problem. If necessary, provide this information to a Software AG Global Support representative. | |
ADA.0600.5001 | PCFMessageAgent could not connect to QueueManager qmgr name; conditionCode=completion code, reasonCode=reason code. |
ExplanationUnable to connect to the queue manager. | |
ActionLook for the reason code returned by WebSphere MQ and take the corrective action mentioned in the WebSphere MQ documentation. | |
ADA.0600.5002 | Unable to execute PCF command name; conditionCode=completion code, reasonCode=reason code. |
ExplanationUnable to execute the PCF command. | |
ActionLook for the reason code returned by WebSphere MQ and take the corrective action mentioned in the WebSphere MQ documentation. Possible causes could be:  Required parameters not provided.Provided parameter values are not valid.Command that is being executed is not supported on the backend platform. | |
ADA.0600.5003 | Error while reading the parameter <parameter name> from the response. conditionCode=<completion code>, reasonCode=<reason code>. |
ExplanationThe response parameter requested is not available in the responses returned from the command execution. | |
ActionNone. | |
ADA.0600.5004 | Error while parsing the PCFCommands metadata file WmPCFCommandMetadataFile.xml. |
ExplanationError occurred with a corrupt xml file or when the xml file not confirming to the DTD. | |
ActionCopy the original WmPCFCommandMetadataFile.xml file into the config folder of the WmMQAdapter package. |