| Error Code | Message | Explanation | User Action |
| AMS0000 | |||
| AMS0001 | AMS_INSERT_STRINGIFIABLE_OBJECT | ||
| AMS1000 | The IBM WebSphere MQ Advanced Message Security Java interceptor failed to obtain the security policy. Reason Code: ''AMS_INSERT_MQ_REASON_CODE'' | The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to obtain the security policy. | See subsequent messages in the exception for more details about the cause of the error. |
| AMS1010 | The IBM WebSphere MQ Advanced Message Security Java interceptor failed to unprotect the received message. | An error occurred when the IBM WebSphere MQ Advanced Message Security Java interceptor was unprotecting the received message. | See subsequent messages in the exception for more details about the cause of the error |
| AMS1011 | An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor failed to get the character set and encoding from the incoming message. | An error ocurred when IBM WebSphere MQ Advanced Message Security Java interceptor was getting the CCSID and encoding from the incoming message. | Retry the operation. If the problem persists, contact your IBM service representative. |
| AMS1020 | Usage: specify the keystore password and private key password java -cp AMS_INSERT_FILENAME com.ibm.mq.ese.config.KeyStoreConfigProtector keystorepass privkeypass | ||
| AMS1030 | Failed to retrieve the following system properties: ''AMS_INSERT_PROPERTY_KEY'' | An error occurred when retrieving certain system properties. | Ensure that the appropriate java permissions are set up in the java.policy for the Java runtime to retrieve these system properties. |
| AMS1035 | Unknown message code: ''AMS_INSERT_AMBI_MESSAGE_CODE'' | The text for the message code could not be found in the resource bundles. | Look up information about the displayed message code. Ensure that the appropriate IBM WebSphere MQ Advanced Message Security language packs are installed on this machine. |
| AMS1040 | Failed to read keystore properties from the keystore configuration file. | An error occurred when reading the properties from the keystore configuration file. | Verify that the keystore configuration file is available and that the Java application has read access to this file. |
| AMS1041 | Failed to retrieve the certificate for alias ''AMS_INSERT_CREDENTIAL_ALIAS'' from the keystore ''AMS_INSERT_FILENAME'' | Certificate for the alias could not be retrieved from the keystore. | Use appropriate certificate management tools to ensure that the keystore contains the certificate for the alias. |
| AMS1042 | Failed to retrieve the certificate for alias ''AMS_INSERT_CREDENTIAL_ALIAS'' from the keystore ''AMS_INSERT_FILENAME'' | Certificate for the alias could not be retrieved from the keystore. | Use appropriate certificate management tools to ensure that the keystore contains the certificate for the alias. |
| AMS1043 | Failed to retrieve the certificate for alias ''AMS_INSERT_CREDENTIAL_ALIAS'' from the keystore ''AMS_INSERT_FILENAME'' | Certificate for the alias could not be retrieved from the keystore. | Use appropriate certificate management tools to ensure that the keystore contains the certificate for the alias. |
| AMS1044 | Failed to retrieve the private key for alias ''AMS_INSERT_CREDENTIAL_ALIAS'' from the keystore ''AMS_INSERT_FILENAME'' | Private key for the alias could not be retrieved from the keystore. | Use appropriate certificate management tools to ensure that the keystore contains the private key for the alias. |
| AMS1045 | Failed to retrieve the private key for alias ''AMS_INSERT_CREDENTIAL_ALIAS'' from the keystore ''AMS_INSERT_FILENAME'' | Private key for the alias could not be retrieved from the keystore. | Use appropriate certificate management tools to ensure that the keystore contains the private key for the alias. |
| AMS1046 | Failed to retrieve aliases from the keystore: ''AMS_INSERT_FILENAME'' | An error occurred when retrieving aliases from the keystore. | Look at subsequent messages for details on actions to perform to fix this problem. |
| AMS1047 | Alias ''AMS_INSERT_CREDENTIAL_ALIAS'' not found in the keystore ''AMS_INSERT_FILENAME'' | An alias is not found in the keystore. | Look at subsequent messages for details on actions to perform to fix this problem. |
| AMS1048 | Failed to retrieve the certificate chain for alias ''AMS_INSERT_CREDENTIAL_ALIAS'' from the keystore ''AMS_INSERT_FILENAME'' | An error occurred when retrieving the certificate chain for an alias from the keystore. | Look at subsequent messages for details on actions to perform to fix this problem. |
| AMS1049 | Failed to verify whether the entry for alias ''AMS_INSERT_CREDENTIAL_ALIAS'' in the keystore ''AMS_INSERT_FILENAME'' contains a certificate. | An error occurred when verifying whether the entry for an alias in the keystore contains a certificate. | Look at subsequent messages for details on actions to perform to fix this problem. |
| AMS1050 | Failed to verify whether the entry for alias ''AMS_INSERT_CREDENTIAL_ALIAS'' in the keystore ''AMS_INSERT_FILENAME'' contains a private key. | An error occurred when verifying whether the entry for an alias in the keystore contains a private key. | Look at subsequent messages for details on actions to perform to fix this problem. |
| AMS1051 | Failed to initialize the keystore ''AMS_INSERT_FILENAME'' | Keystore initialization failed. | Look at subsequent messages for details on actions to perform to fix this problem. |
| AMS1052 | Failed to protect the password for alias ''AMS_INSERT_CREDENTIAL_ALIAS'' in keystore ''AMS_INSERT_FILENAME'' | An error occurred when protecting the password for an alias in the keystore. | Look at subsequent messages for details on actions to perform to fix this problem. |
| AMS1053 | Failed to unprotect the password for alias ''AMS_INSERT_CREDENTIAL_ALIAS'' in keystore ''AMS_INSERT_FILENAME'' | An error occurred when unprotecting the password for an alias in the keystore. | Look at subsequent messages for details on actions to perform to fix this problem. |
| AMS1054 | Failed to get the certificates for these recipients: ''AMS_INSERT_RECIPIENTS_NAMES'' | An error occurred when retrieving certificates for recipients. | Verify that the certificates for these recipients are in the local keystore or in the user registry. |
| AMS1055 | An error occurred when trying to retrieve the recipient certificates. | An error occurred when trying to retrieve the recipient certificates. | Look at subsequent messages for details on actions to perform to fix this problem. |
| AMS1056 | The message does not contain an IBM WebSphere MQ Advanced Message Security header or it contains a header that is not valid. | The message does not contain an IBM WebSphere MQ Advanced Message Security header or it contains a header that is not valid. | Make sure that the IBM WebSphere MQ Advanced Message Security security policy is the same for the sender and the receiver. |
| AMS1057 | The IBM WebSphere MQ Advanced Message Security header could not be converted from ''AMS_INSERT_CHARACTER_ENCODING'' to UTF8. | An error occurred when converting the IBM WebSphere MQ Advanced Message Security header to UTF8. | Make sure this character encoding is supported by your Java runtime. If the problem persists, contact your IBM service representative. |
| AMS1058 | The IBM WebSphere MQ Advanced Message Security header could not be converted from ''AMS_INSERT_CHARACTER_ENCODING'' to UTF8. | An error occurred when converting the IBM WebSphere MQ Advanced Message Security header to UTF8. | Make sure this character encoding is supported by your Java runtime. If the problem persists, contact your IBM service representative. |
| AMS1059 | An internal has error occurred. The IBM WebSphere MQ Advanced Message Security header could not be converted to an array of bytes. | An internal error occurred when converting the IBM WebSphere MQ Advanced Message Security header to an array of bytes. | Retry the failing operation. If the problem persists, contact your IBM service representative. |
| AMS1060 | The format of the recipient name ''AMS_INSERT_SUBJECT_NAME'' is not valid. | The format of the recipient name is not valid. | Set the extended attribute for the recipients to a valid value. |
| AMS1061 | The specified alias ''AMS_INSERT_CREDENTIAL_ALIAS'' was not found in the keystore ''AMS_INSERT_FILENAME'' | The alias could not be located on the keystore. | Use appropriate certificate management tools to ensure that the keystore contains the alias specified. |
| AMS1062 | The specified alias ''AMS_INSERT_CREDENTIAL_ALIAS'' was not found in the keystore ''AMS_INSERT_FILENAME'' | The alias could not be located on the keystore. | Use appropriate certificate management tools to ensure that the keystore contains the alias specified. |
| AMS1063 | The alias ''AMS_INSERT_CREDENTIAL_ALIAS'' is not a key entry. Keystore: ''AMS_INSERT_FILENAME'' | The alias specified is not a key entry. | Use appropriate certificate management tools to ensure that the alias specified is a key entry. |
| AMS1064 | The keystore password can only contain ASCII characters. | The keystore password contains non-ASCII characters. | Change your keystore password to contain only ASCII characters. |
| AMS1065 | Could not read following keys from keystore configuration file: ''AMS_INSERT_PROPERTY_KEY''. | An error occurred when reading properties from the keystore configuration file. | Verify that the property in the keystore configuration file has correct value. |
| AMS1066 | The PKCS11 keystore initialized succesfully, PKCS11 configuration: ''AMS_INSERT_PKCS11_PROVIDER_INFORMATION''. | The PKCS11 hardware based keystore has been successfully initialized. | No action is required. |
| AMS1100 | The IBM WebSphere MQ Advanced Message Security interceptor could not parse the keystore configuration file. | The IBM WebSphere MQ Advanced Message Security interceptor could not parse the keystore configuration file. | Make sure the keystore configuration file contains all required keys and does not contain duplicate keys. |
| AMS1101 | The IBM WebSphere MQ Advanced Message Security keystore configuration file contains duplicate key: ''AMS_INSERT_CONFIG_KEY''. | The IBM WebSphere MQ Advanced Message Security keystore configuration file contains duplicate key. | Make sure the keystore configuration file contains all required keys and does not contain duplicate keys. |
| AMS1102 | The IBM WebSphere MQ Advanced Message Security keystore configuration file must contain absolute path ''AMS_INSERT_FILENAME''. | IBM WebSphere MQ Advanced Message Security expected absolute path but found relative one. | Make sure the keystore configuration file contains absolute path. |
| AMS1120 | An internal error occurred: the quality of protection received by the IBM WebSphere MQ Advanced Message Security Java interceptor is not valid. Quality of protection: ''AMS_INSERT_QUALITY_OF_PROTECTION'' | The quality of protection received by the Java interceptor is not valid. | Retry the failing operation. If the problem persists, contact your IBM service representative. |
| AMS1121 | An internal error occurred: the quality of protection received by the IBM WebSphere MQ Advanced Message Security Java interceptor is not valid. Quality of protection: ''AMS_INSERT_QUALITY_OF_PROTECTION'' | The quality of protection received by the Java interceptor is not valid. | Retry the failing operation. If the problem persists, contact your IBM service representative. |
| AMS1122 | An internal error occurred: the encryption strength ''AMS_INSERT_ENCRYPTION_STRENGTH'' received by the IBM WebSphere MQ Advanced Message Security Java interceptor is not valid. | The encryption strength received by the Java interceptor is not valid. | Retry the failing operation. If the problem persists, contact your IBM service representative. |
| AMS1123 | An internal error occurred: the signature algorithm ''AMS_INSERT_SIGNATURE_ALGORITHM'' received by the IBM WebSphere MQ Advanced Message Security Java interceptor is not valid. | The signature algorithm received by the Java interceptor is not valid. | Retry the failing operation. If the problem persists, contact your IBM service representative. |
| AMS1124 | An internal error occurred: the signature algorithm ''AMS_INSERT_SIGNATURE_ALGORITHM'' received by the IBM WebSphere MQ Advanced Message Security Java interceptor is not valid. | The signature algorithm received by the Java interceptor is not valid. | Retry the failing operation. If the problem persists, contact your IBM service representative. |
| AMS1125 | The IBM WebSphere MQ Advanced Message Security Java interceptor failed to protect message. | The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to protect the message. | See subsequent messages in the exception for more details about the cause of the error. |
| AMS1126 | The IBM WebSphere MQ Advanced Message Security Java interceptor failed to protect message. | The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to protect the message. | See subsequent messages in the exception for more details about the cause of the error. |
| AMS1127 | An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor found more than one sender certificate in the protected message. | Only one sender certificate is expected in the protected message. | Retry the failing operation. If the problem persists, contact your IBM service representative. |
| AMS1128 | An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor failed to find the certificate of the sender in the protected message. | The Java interceptor failed to find the certificate of the sender. The protected message is expected to contain the certificate of the sender. | Retry the failing operation. If the problem persists, contact your IBM service representative. |
| AMS1129 | An internal error occurred: the syntax of the protected message received by IBM WebSphere MQ Advanced Message Security Java interceptor is not valid. | The syntax of the protected message received by the Java interceptor is not valid. | Ensure that your security policy is specified correctly and retry the failing operation. If the problem persists, contact your IBM service representative. |
| AMS1130 | The IBM WebSphere MQ Advanced Message Security Java interceptor failed to unprotect message. | The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to unprotect the message. | See subsequent messages in the exception for more details about the cause of the error. |
| AMS1131 | An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor failed to find any recipients from the received message. | The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to obtain any recipients from the received message. | Retry the failing operation. If the problem persists, contact your IBM service representative. |
| AMS1132 | The certificate of the sender with the subject name ''AMS_INSERT_CERTIFICATE_SUBJECT'' is not valid. | The certificate of the sender is not valid. | See subsequent messages in the exception for more details about the cause of the error. |
| AMS1133 | The certificate of the sender with the subject name ''AMS_INSERT_CERTIFICATE_SUBJECT'' is not valid. | The certificate of the sender is not valid. | See subsequent messages in the exception for more details about the cause of the error. |
| AMS1134 | The certificate of the recipient with the subject name ''AMS_INSERT_CERTIFICATE_SUBJECT'' is not valid. | The certificate of the recipient is not valid. | See subsequent messages in the exception for more details about the cause of the error. |
| AMS1135 | The protected message type does not match the quality of protection (QOP) specified on the objectspace. The expected QOP is ''AMS_INSERT_EXPECTED_QUALITY_OF_PROTECTION'' whereas the actual one is ''AMS_INSERT_QUALITY_OF_PROTECTION'' | The protected message type does not match the QOP specified on the object space. | Verify that the security policy is correctly specified. |
| AMS1136 | The IBM WebSphere MQ Advanced Message Security Java interceptor failed to decrypt the protected message. | The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to decrypt the protected message. | See subsequent messages in the exception for more details about the cause of the error. |
| AMS1137 | The IBM WebSphere MQ Advanced Message Security Java interceptor failed to verify the protected message signature. | The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to verify the protected message signature. | See subsequent messages in the exception for more details about the cause of the error. |
| AMS1138 | The IBM WebSphere MQ Advanced Message Security Java interceptor failed to verify the certificate trust chain. The certificate subject name: ''AMS_INSERT_CERTIFICATE_SUBJECT'' | The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to verify the certificate trust chain. | See subsequent messages in the exception for more details about the cause of the error. |
| AMS1139 | The protected message encryption mismatch. The expected encryption strength is ''AMS_INSERT_EXPECTED_ENCRYPTION_STRENGTH'' whereas the actual encryption strength is ''AMS_INSERT_ENCRYPTION_STRENGTH'' | The protected message encryption does not match the one specified on the object space. | Verify that the security policy is correctly specified. |
| AMS1140 | The receiver of this encrypted message is not on the message recipient list ''AMS_INSERT_DISTINGUISHED_NAME'' | The certificate of a user that is receiving a message is not on the message RecipientsInfo list. | Verify that the user is on a recipients list in a security policy definition. |
| AMS1200 | The certificate with the following subject name ''AMS_INSERT_CERTIFICATE_SUBJECT'' is not yet valid. The certificate will become valid after ''AMS_INSERT_DATE'' | The certificate is not yet within its validity period. | Retry the failing operation as soon as the certificate is valid or modify your configuration to use a valid certificate. |
| AMS1201 | The certificate with the following subject name ''AMS_INSERT_CERTIFICATE_SUBJECT'' is expired. The expiration date of the certificate is ''AMS_INSERT_DATE'' | The certificate is expired. | Modify your configuration to use a valid certificate. |
| AMS1202 | The IBM WebSphere MQ Advanced Message Security Java interceptor failed to verify the validity period of the certificate. The subject name of the certificate is ''AMS_INSERT_CERTIFICATE_SUBJECT'' | The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to verify the validity period of a certificate. | Retry the failing operation. If the problem persists, contact your IBM service representative. |
| AMS1203 | A key usage bit that is not valid was found on the certificate with the following subject name ''AMS_INSERT_CERTIFICATE_SUBJECT''. The ''AMS_INSERT_USAGE_BIT_NAME'' key usage bit should be set to ''AMS_INSERT_EXPECTED_USAGE_BIT_VALUE'' instead of ''AMS_INSERT_USAGE_BIT_VALUE'' | A key usage bit that is not valid was found on the certificate. | Modify your configuration to use a certificate that has a valid key usage extension. Consult the Administration guide for more details about certificate settings. |
| AMS1204 | An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor failed to obtain the encryption algorithm name. | An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor failed to obtain the encryption algorithm name. | Retry the failing operation. If the problem persists, contact your IBM service representative. |
| AMS1205 | The IBM WebSphere MQ Advanced Message Security Java interceptor failed to obtain any recipient certificate. | The IBM WebSphere MQ Advanced Message Security Java interceptor attempted to encrypt a message, but it did not find certificates of recipients | Make sure that a keystore contains all certificates specifed in the appropriate security policy. |
| AMS1206 | The IBM WebSphere MQ Advanced Message Security Java interceptor failed to obtain any recipient certificate. | The IBM WebSphere MQ Advanced Message Security Java interceptor attempted to encrypt a message, but it did not find certificates of recipients | Make sure that a keystore contains all certificates specifed in the appropriate security policy. |
| AMS1207 | An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor failed to obtain the signature algorithm name. | An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor failed to obtain the signature algorithm name. | Retry the failing operation. If the problem persists, contact your IBM service representative. |
| AMS1208 | No proper key bit was found for the certificate for the subject name ''AMS_INSERT_SUBJECT_NAME''. The actual values are: ''AMS_INSERT_KEY_VALUE_LIST'', the proper values are: ''AMS_INSERT_EXPECTED_KEY_VALUE_LIST'', the state of at least one bit should match. | A key usage bit that is not valid was found on the certificate. | Modify your configuration to use a certificate that has a valid key usage extension. Consult the Administration guide for more details about certificate settings. |
| AMS1209 | IBM WebSphere MQ Advanced Message Security Java interceptor failed to verify CRL signature signed by ''AMS_INSERT_ISSUER_NAME'' | IBM WebSphere MQ Advanced Message Security Java interceptor failed to verify CRL signed by the given issuer DN | Make sure certificate of the issuer is present in the local keystore. |
| AMS1210 | The Certificate Revocation List ''AMS_INSERT_CRL_NAME'' could not be loaded | The CRL cannot be found or accessed. | Modify your configuration to point to a valid CRL. Make sure the CRL can be read. |
| AMS1211 | The IBM WebSphere MQ Advanced Message Security Java interceptor could not access Certificate Revocation List. | The CRL cannot be found or accessed. | Modify your configuration to point to a valid CRL. Make sure the CRL can be read. |
| AMS1212 | The IBM WebSphere MQ Advanced Message Security Java interceptor failed to validate the certificate. A certificate with BasicConstraint CA set to true cannot be used as End Entity. The subject name is ''AMS_INSERT_SUBJECT_NAME'' | The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to verify the certificate. | |
| AMS1213 | The IBM WebSphere MQ Advanced Message Security Java interceptor failed to validate the certificate. A certificate with the subject name ''AMS_INSERT_SUBJECT_NAME'' has been revoked. | The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to verify the certificate. | |
| AMS1300 | IBM WebSphere MQ Advanced Message Security internal error: queue manager information could not be saved.(''AMS_INSERT_MQ_ERROR_CODE'') | The IBM WebSphere MQ Advanced Message Security interceptor could not save the queue manager connection (hconn) information because an internal error occurred. | If the problem occurs persistently, contact your IBM service representative. |
| AMS1310 | IBM WebSphere MQ Advanced Message Security could not resolve current queue name from the object handle.(''AMS_INSERT_MQ_ERROR_CODE'') | The IBM WebSphere MQ Advanced Message Security interceptor could not resolve the current queue name from the object handle. The queue might be opened by some internal WebSphere MQ application program interface (API) other than Message Queue Interface (MQI). | Make sure the application does not use internal WebSphere MQ APIs to open the queue. If the problem persists, contact your IBM service representative. |
| AMS1311 | MQOPEN() call failed: reason code (''AMS_INSERT_MQ_REASON_CODE''). | The IBM WebSphere MQ Advanced Message Security interceptor call to the WebSphere MQ MQOPEN() function failed with the indicated error. | Consult the WebSphere MQ documentation for an explanation of the error code and suggested corrective action. Ensure that the queue manager is operational, the queue exists. |
| AMS1312 | MQCLOSE() call failed, reason code (''AMS_INSERT_MQ_REASON_CODE''). | The IBM WebSphere MQ Advanced Message Security interceptor call to the WebSphere MQ MQCLOSE() function failed with the indicated WebSphere MQ reason code. | Consult the IBM WebSphere MQ documentation for an explanation of the error code and suggested corrective action. Ensure that the queue manager is operational, protected object space are present and correct. Make sure that IBM WebSphere MQ Advanced Message Security are configured and running correctly. |
| AMS1313 | IBM WebSphere MQ Advanced Message Security internal error: message could not be protected because the specified signature algorithm ''AMS_INSERT_SIGNATURE_ALGORITHM'' is not valid. | The unexpected signature algorithm has been specified | This is an internal error. Contact your IBM service representative |
| AMS1325 | IBM WebSphere MQ Advanced Message Security internal error: queue information could not be resolved from the current queue object handle. (''AMS_INSERT_MQ_ERROR_CODE'') | The IBM WebSphere MQ Advanced Message Security interceptor could not resolve queue information from the current queue object handle because the current queue was not opened via IBM WebSphere MQ Advanced Message Security, or it was closed. | Make sure that the queue has not already been opened by another WebSphere MQ application and that it has not been previously closed. If the problem persists, contact your IBM service representative. |
| AMS1326 | IBM WebSphere MQ Advanced Message Security internal error: could not find local queue manager CodedCharSetId (''AMS_INSERT_MQ_ERROR_CODE''). | The IBM WebSphere MQ Advanced Message Security interceptor could not find the local queue manager's CodedCharSetId because an internal error occurred. | Make sure that the queue manager is connected through IBM WebSphere MQ Advanced Message Security. If the problem persists, contact your IBM service representative. |
| AMS1327 | Quality of protection ''AMS_INSERT_QUALITY_OF_PROTECTION_NO'' for queue ''AMS_INSERT_Q_NAME'' is invalid | The IBM WebSphere MQ Advanced Message Security interceptor detected that the quality of protection specified in the security policy for the queue is invalid. | Make sure that the encryption and signature algorithms specified for the queue in the IBM WebSphere MQ Advanced Message Security security policy definition have valid values. |
| AMS1328 | Message with no protection has been put into the queue ''AMS_INSERT_Q_NAME''. | The IBM WebSphere MQ Advanced Message Security interceptor has successfully put a message with the 'none' protection level onto the selected queue. | No action is required. |
| AMS1329 | Message with integrity protection has been put into the queue ''AMS_INSERT_Q_NAME''. | The IBM WebSphere MQ Advanced Message Security interceptor has successfully put a message with the 'integrity' protection level onto the selected queue. | No action is required. |
| AMS1330 | Message with privacy protection has been put into the queue ''AMS_INSERT_Q_NAME''. | The IBM WebSphere MQ Advanced Message Security interceptor has successfully put a message with the 'privacy' protection level onto the selected queue. | No action is required. |
| AMS1331 | IBM WebSphere MQ Advanced Message Security internal error: could not inquire about queue manager properties (''AMS_INSERT_MQ_ERROR_CODE''). | The IBM WebSphere MQ Advanced Message Security interceptor could not inquire about queue manager's properties because an internal error occurred. | Make sure that the queue manager is connected through IBM WebSphere MQ Advanced Message Security. If the problem persists, contact your IBM service representative. |
| AMS1340 | IBM WebSphere MQ Advanced Message Security internal error: queue information could not be resolved from the current queue object handle. (''AMS_INSERT_INTERNAL_ERROR_CODE'') | The IBM WebSphere MQ Advanced Message Security interceptor could not resolve queue information from the current queue object handle because the current queue was not opened by IBM WebSphere MQ Advanced Message Security, or it was closed. | Make sure that the queue is not already been opened by another WebSphere MQ application, and that it has not been previously closed. If the problem persists, contact your IBM service representative. |
| AMS1341 | IBM WebSphere MQ Advanced Message Security found a valid 'PDMQ' format header in the current message. | IBM WebSphere MQ Advanced Message Security interceptor found a valid IBM WebSphere MQ Advanced Message Security header in the current message. | No action is required. |
| AMS1342 | The 'PDMQ' format header from the current message is invalid. | The IBM WebSphere MQ Advanced Message Security interceptor did not find a valid IBM WebSphere MQ Advanced Message Security header in the the current message. | Check the Quality of Protection (QoP) setting for the queue object. If the QoP setting for the queue is not 'none', make sure that no IBM WebSphere MQ plain text messages are routed to this queue. |
| AMS1343 | Message quality of protection (''AMS_INSERT_QUALITY_OF_PROTECTION'') does not match the quality of protection (''AMS_INSERT_EXPECTED_QUALITY_OF_PROTECTION'') set for the queue ''AMS_INSERT_Q_NAME''. | The IBM WebSphere MQ Advanced Message Security interceptor detected a quality of protection (QoP) mismatch between the queue and a message in the queue. QoP mismatches usually occur because the queue QoP is changed between the message put and get. | Make sure that the same queue quality of protection is used for the message put and get. When the queue QoP is changed, clean up all messages in the queue before resuming normal operation. |
| AMS1344 | ''AMS_INSERT_Q_NAME'' - message was signed by ''AMS_INSERT_DISTINGUISHED_NAME'' at ''AMS_INSERT_TIMESTAMP'' using ''AMS_INSERT_SIGNATURE_ALGORITHM''. | This is an informational message used to indicate that a message was signed, and to display the signer's name, message timestamp and signature algorithm used. | No action is required. |
| AMS1345 | ''AMS_INSERT_Q_NAME'' - message was signed and encrypted by ''AMS_INSERT_DISTINGUISHED_NAME'' at ''AMS_INSERT_TIMESTAMP'' using ''AMS_INSERT_SIGNATURE_ALGORITHM'' and ''AMS_INSERT_ENCRYPTION_ALGORITHM''. | This is an informational message used to indicate that a message was signed and encrypted, and to display the signer's name, message timestamp, signature algorithm name and encryption algorithm name. | No action is required. |
| AMS1346 | Message does not have a valid protection type. | The IBM WebSphere MQ Advanced Message Security interceptor detected an invalid protection type in a message header. This usually occurs because the IBM WebSphere MQ message header is not valid. | Retry the operation. If the problem persists, contact your IBM service representative. |
| AMS1347 | The IBM WebSphere MQ Advanced Message Security interceptor has put a defective message on error handling queue ''AMS_INSERT_Q_NAME''. | This is an informational message that indicates the IBM WebSphere MQ Advanced Message Security put a message it could not interpret on the specified error handling queue. | Make sure only valid messages are put onto queues protected by IBM WebSphere MQ Advanced Message Security. |
| AMS1348 | The IBM WebSphere MQ Advanced Message Security interceptor failed to put a defective message on error handling queue. MQ reason code (''AMS_INSERT_MQ_REASON_CODE'') | The IBM WebSphere MQ Advanced Message Security interceptor was unable to put a message it could not interpret on the error handling queue because the indicated IBM WebSphere MQ error occurred. | Consult the IBM WebSphere MQ documentation for more information about the reason code. If the problem persists, contact your IBM service representativ. |
| AMS1349 | IBM WebSphere MQ Advanced Message Security internal error: message could not be converted from source CCSID ''AMS_INSERT_SOURCE_CCSID'' to target CCSID ''AMS_INSERT_TARGET_CCSID''. IBM WebSphere MQ compcode ''AMS_INSERT_MQ_COMPLETION_CODE'' : reason ''AMS_INSERT_MQ_REASON_CODE''. | The IBM WebSphere MQ Advanced Message Security interceptor could not convert the message from the source Coded Character Set Identifier (CCSID) to target CCSID. | Consult the IBM WebSphere MQ documentation for the completion code and reason code, take corrective action. If the problem persists, contact your IBM service representative. |
| AMS1350 | IBM WebSphere MQ Advanced Message Security internal error: message could not be retrieved from the queue. MQGET() failed. IBM WebSphere MQ compcode ''AMS_INSERT_MQ_COMPLETION_CODE'' : reason ''AMS_INSERT_MQ_REASON_CODE''. | The IBM WebSphere MQ Advanced Message Security interceptor could not get the message from the queue. | Consult the IBM WebSphere MQ documentation for the completion code and reason code, take corrective action. If the problem persists, contact your IBM service representative. |
| AMS1351 | IBM WebSphere MQ Advanced Message Security internal error: unprotected message size ''AMS_INSERT_MESSAGE_SIZE'' bytes does not match the original message size ''AMS_INSERT_ORIGINAL_MESSAGE_SIZE'' bytes. | After unprotecting, the message size does not match the original message size. The message header might have been corrupted or tampered with. | Check the message which has been put on the dead letter queue and the audit logs to find the cause of the error and the origin of the message. If the problem persists, contact your IBM service representative. |
| AMS1352 | IBM WebSphere MQ Advanced Message Security internal error: unprotected message QoP does not match QoP indicated in the header. Queue manager is ''AMS_INSERT_QM_NAME'', queue is ''AMS_INSERT_Q_NAME'', msgId is ''AMS_INSERT_MESSAGE_ID'' | During unprotecting the mismatch between the message buffer quality of protection type and the one specified by the IBM WebSphere MQ Advanced Message Security header was discovered. The message header might have been corrupted or tampered with. | Check the message which has been put into the dead letter queue and the audit logs to find the cause of the error and the origin of the message. If the problem persists, contact your IBM service representative. |
| AMS1353 | Message with quality of protection (''AMS_INSERT_QUALITY_OF_PROTECTION'') higher than (''AMS_INSERT_EXPECTED_QUALITY_OF_PROTECTION'') set for the queue ''AMS_INSERT_Q_NAME'' has been accepted. | The IBM WebSphere MQ Advanced Message Security interceptor detected a quality of protection (QoP) mismatch between the queue and a message in the queue. QoP mismatch usually occurs when the QoP of the queue is changed between the message put and get. | Make sure that the same queue quality of protection is used for the message put and get. When the QoP of the queue is changed, remove all messages from the queue before resuming any operation. |
| AMS1354 | Message signer is not in the list of authorised signers. | The IBM WebSphere MQ Advanced Message Security interceptor detected that the message is signed by an unauthorised party. | Make sure the sender is mentioned in the list of allowed signers. |
| AMS1355 | Message could not be moved from queue (''AMS_INSERT_Q_NAME'') to error handling queue. IBM WebSphere MQ completion code (''AMS_INSERT_MQ_COMPLETION_CODE''), reason code (''AMS_INSERT_MQ_REASON_CODE''). | The IBM WebSphere MQ Advanced Message Security interceptor failed to remove the message before it attempted to put it on error handling queue. | Consult the IBM WebSphere MQ documentation for the completion code and reason code, take corrective action. If the problem persists, contact your IBM service representative. |
| AMS1356 | Message too big to fit the buffer, queue (''AMS_INSERT_Q_NAME''), MQ completion code (''AMS_INSERT_MQ_COMPLETION_CODE''), reason code (''AMS_INSERT_MQ_REASON_CODE''). | The IBM WebSphere MQ Advanced Message Security interceptor failed to unprotect data because provided buffer is too small | Issue MQGET with bigger buffer |
| AXISWMQ1001 | Invalid protocol in URI. | The protocol specified for the URI is not a recognised type. | The URI must use the JMS protocol. e.g. jms:/queue?destination=SOAPJ.demos@WMQSOAP.DEMO.QM. |
| AXISWMQ1002 | Invalid Destination type. | The URI either did not specify a destination, or it is incorrectly formated. | Refer to the documentation for the correct URI format. e.g. jms:queue:mqQueue |
| AXISWMQ1003 | Invalid Destination type. | The URI either did not specify a destination, or it is incorrectly formated. | The URI must specify the destination type "/queue". e.g. jms:/queue?destination=SOAPJ.demos@WMQSOAP.DEMO.QM. |
| AXISWMQ1004 | Destination must be the first parameter in the URI. | The URI either did not specify a destination, or it is incorrectly formated. | Destination must be the first parameter in the URI. Refer to the documentation for the correct URI format. |
| AXISWMQ1005 | URI attribute "AXISWMQ_ATTRIBUTE" must be set to "AXISWMQ_ATTRIBUTE_VALUE" | The URI either did not specify the value for "{0}" or its value differs from the required value of "{1}". | Change the value of "{0}" in the URI to "{1}". Refer to the documentation for the correct URI format. |
| AXISWMQ1006 | URI attribute "AXISWMQ_ATTRIBUTE" is missing. | The URI did not specify the value for "{0}". | The URI must be changed to specify a value for attribute "{0}". Refer to the documentation for the correct URI format. |
| AXISWMQ1007 | Invalid value "AXISWMQ_ATTRIBUTE_VALUE" for "AXISWMQ_ATTRIBUTE". | The URI specified an incorrect value for attribute "{1}". | The URI must be changed to specify a valid value for attribute "{1}". Refer to the documentation for the correct URI format. |
| AXISWMQ1008 | Client attribute not valid for binding "server". | The URI specified a client property, which conflicts with the binding value of "server". | The URI must be changed either to specify a binding value of "client", or to remove client specific attributes from the URI. Refer to the documentation for the correct URI format. |
| AXISWMQ1009 | CCDT ignored due to client attributes specified on URI. | The URI specified client attributes and therefore the CCDT specified has been ignored. | The URI must be changed to remove client specific attributes if you wish to use the CCDT. Refer to the documentation for the correct URI format. |
| AXISWMQ1010 | Client attribute "AXISWMQ_ATTRIBUTE" required for binding "client". | The URI did not specify the value for "{0}". | The URI must be changed to specify a value for attribute "{0}". Refer to the documentation for the correct URI format. |
| AXISWMQ1011 | Invalid Connection Factory Attribute. | The URI specified a Connection Factory attribute which is not formatted correctly. | The URI must be changed to correct the Connection Factory attribute. Refer to the documentation for the correct URI format. |
| AXISWMQ1012 | Connection Factory property "AXISWMQ_CF_PROP" not recognised. | The URI specified a Connection Factory property which is not recognised and has been ignored. | The URI must be changed either to remove, or correct, the Connection Factory property "{0}". Refer to the documentation for the correct URI format. |
| AXISWMQ1013 | Invalid destination name. | The URI destination name "{0}" is incorrect. | The URI must be changed to include a valid destination name. For example, jms:/queue?destination=SOAPJ.demos@WMQSOAP.DEMO.QM. Refer to the documentation for the correct URI format. |
| AXISWMQ1014 | URI syntax incorrect. | The URI "{0}" violates RFC 2396. | See linked Exception for further details. |
| AXISWMQ1015 | Problem parsing name/value String "AXISWMQ_STRING" in URI string. | An error occurred when decoding the string using Character Set "{1}". | See linked Exception for further details. |
| AXISWMQ2001 | Problem creating JMS Destination. | A problem occurred creating the required JMS resources for the destination string specified. | See linked Exception for further details. |
| AXISWMQ2002 | Problem creating JMS Connection Factory. | A problem occurred creating the JMS Connection Factory. The JMS Connection Factory is required to create a connection to the Queue Manager. | See linked Exception for further details. |
| AXISWMQ2003 | Problem setting URI Connection Factory properties. | A problem occurred when properties specified on the URI were set on the JMS Connection Factory. | One of the values specified in the URI Connection Factory Attribute may be invalid. See linked Exception for further details. |
| AXISWMQ2004 | Problem creating JMS resources. | A problem occurred creating one of the JMS resources required to action the request. | See linked Exception for further details. |
| AXISWMQ3001 | Problem creating request. | A problem occurred creating the request. | See linked Exception for further details. |
| AXISWMQ3002 | The input stream of the reply message is NULL. | A reply was expected, however the reply was NULL. | Check the definition of the service method in the WSDL as it might specify a reply is expected. |
| AXISWMQ3003 | Problem parsing reply. | A reply was expected and received, however there was an error parsing it. | See linked Exception for further details. |
| AXISWMQ3004 | Timeout receiving reply. | A reply was expected, however the operation timed out before one could be received. | Check that the service is running. If the service is running increase the timeout. |
| AXISWMQ3005 | A WMQ report message has been returned in response to the request message. | The request message was rejected as a poison message by the service and could not be processed. This might be due to an incorrectly formatted request, unrecognised service method, or a failure in the service method. | Check the message is encoded correctly and the required service is available and correctly configured. |
| AXISWMQ3006 | The received message "AXISWMQ_MSGID" was not a JMS bytes or a JMS text message. | A message has been received but it is not of the correct type. It must be either a JMS bytes message or a JMS text message. | Check the origin and contents of the message and determine the cause for it being incorrect. |
| AXISWMQ3007 | The received message "AXISWMQ_MSGID" could not be de-serialised | The message format or contents is not consistent with the default encoder and cannot be interpreted as a SOAP/JMS message. | Review the linked exceptions for further details. |
| AXISWMQ3008 | Invalid value "AXISWMQ_TRANS_PARAM_VAL" for "AXISWMQ_TRANS_PARAM". | The transport entry in axis2.xml for jms specified an incorrect value for parameter "{1}". | The transport entry must be changed to specify a valid value for parameter "{1}". Refer to the documentation for the allowed values. |
| JMSCC0001 | An internal error occurred. It was not possible to instantiate a required class: ''XMSC_INSERT_EXCEPTION''. | Save any generated output files and use either the WMQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. | |
| JMSCC0002 | WebSphere MQ classes for JMS attempted to set an invalid client ID on a connection. | An application attempted to set the client ID property of a valid connection to null, or attempted to set the clientId property of an invalid connection. | The clientId property on a connection can only be set once, only to a non-null value, and only before the connection is used. Ensure that the connection is valid and that the client ID is not null. |
| JMSCC0003 | The specified value ''XMSC_INSERT_VALUE'' is not allowed for ''XMSC_INSERT_NAME''. | The given value is not allowed for the property specified. | Change the value to a value that is supported for the property. |
| JMSCC0004 | Calling receive will not return a message for a connection that is stopped. | The JMS specification says that calling the receive() method must not return a message if the connection is stopped. Calling receiveNoWait or receive with a timeout will return null when the timeout expires. Calling receive with no timeout will not return until the connection is started or closed or the application terminates. | Start the connection by calling javax.jms.Connection.start(). |
| JMSCC0005 | The specified value ''XMSC_INSERT_VALUE'' is not allowed for ''XMSC_INSERT_NAME''. | The given value is not allowed for the property specified. | Change the value to a value that is supported for the property. |
| JMSCC0007 | An exception was received during the call to the method ''XMSC_INSERT_METHOD'': ''XMSC_INSERT_EXCEPTION''. | An exception was thrown by another component while the specified method was running. | See the linked exception for more information. |
| JMSCC0008 | This connection is closed. | An application called a method that must not be used after the connection is closed. | Ensure that the connection is not closed before calling the method. |
| JMSCC0011 | The method ''XMSC_INSERT_METHOD'' is not permitted in this container. | A method was called that is not permitted in the current container. | Remove the call to the method. |
| JMSCC0014 | It is not valid to call the ''XMSC_INSERT_METHOD'' method on a nontransacted session. | The application called a method that must not be called on a nontransacted session. | Change the application program to remove this behavior. |
| JMSCC0020 | This session is closed. | An application called a method that must not be used after the session is closed. | Ensure that the session is not closed before calling the method. |
| JMSCC0021 | It is not valid to call the ''XMSC_INSERT_METHOD'' method on a transacted session. | The application called a method that must not be called on a transacted session. | Change the application program to remove this behavior. |
| JMSCC0026 | This message producer is closed. | An application called a method that must not be used after the message producer is closed. | Ensure that the message producer is not closed before calling the method. |
| JMSCC0029 | A destination must be specified when sending from this producer. | The producer was created with a null destination and a destination was not supplied on the send method. | Change the application so that a send() method that specifies a destination is used, or specify a destination when creating the producer. |
| JMSCC0030 | It is not valid to specify a destination when sending from this producer. | The producer was created with a specified destination; it is not valid to specify a destination again when sending a message. | Change the application so that a send method that does not specify a destination is used, or specify a null destination when creating the producer. |
| JMSCC0032 | This message consumer is closed. | An application called a method that must not be used after the message consumer is closed. | Ensure that the message consumer is not closed before calling the method. |
| JMSCC0033 | A synchronous method call is not permitted when a session is being used asynchronously: ''XMSC_INSERT_METHOD''. | The JMS specification does not permit the use of a session for synchronous methods when asynchronous message delivery is running. | Create a separate session if you wish to use both synchronous methods and asynchronous delivery simultaneously. |
| JMSCC0034 | The asynchronous delivery mechanism is in an inconsistent state in method: ''XMSC_INSERT_METHOD''. | An unexpected sequence of events has been detected during delivery of messages to a message-driven bean (MDB). This may be caused by client programming application errors. | Check the application server log files for other problems associated with the message-driven bean. Save any generated output files and use either the WMQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. |
| JMSCC0037 | A runtime exception was thrown by the MessageListener.onMessage() method. | A message consumer with a registered message listener received an exception from the onMessage() method. | The onMessage() method should be changed to avoid throwing exceptions. |
| JMSCC0038 | The user does not have authorization to carry out this operation. See the linked exception for details. | The linked exception contains details of the authority that is required to carry out this operation. | The administrator must grant the required authority to the relevant user. |
| JMSCC0039 | The type ''XMSC_INSERT_TYPE'' is not valid for use as object property ''XMSC_INSERT_PROPERTY''. | An application tried to set an object property using an object type that is not permitted by the JMS specification. | Use a permitted object type. The primitive wrapper classes and String objects are permitted object types. |
| JMSCC0040 | An exception occurred while receiving a message: ''XMSC_INSERT_EXCEPTION''. | While receiving a message an exception was thrown that caused the operation to fail. | Examine the specified exception, and linked exception object for more information. |
| JMSCC0041 | The conversion of the item ''XMSC_INSERT_PROPERTY'' from type ''XMSC_INSERT_TYPE'' to type ''XMSC_INSERT_OTHER_TYPE'' is not permitted. | Conversion between the two specified data types is not permitted by the JMS specification. | Retrieve the named item using one of the permitted conversions. |
| JMSCC0042 | The message field ''XMSC_INSERT_FIELD'' has not been set. | An application attempted to retrieve the value of a field that has not been set. | Set the value of the field before retrieving it. |
| JMSCC0043 | A null or empty string field name is not permitted. | A user application has attempted to set a field using a name that is not valid, for example, null or empty String. | Use a valid field name. |
| JMSCC0044 | It is not permitted to call method ''XMSC_INSERT_METHOD'' on the message because the message body is read-only. | A user application has attempted to set a read-only message body. | Change the application program to remove this behavior, or call the clearBody() method first. |
| JMSCC0045 | It is not permitted to call method ''XMSC_INSERT_METHOD'' on the message because the message properties are read-only. | A user application has attempted to set a read-only message property. | Change the application program to remove this behavior, or call the clearProperties() method first. |
| JMSCC0046 | It is not permitted to call method ''XMSC_INSERT_METHOD'' on the message because the message body is write-only. | A user application has attempted to read a write-only message body. | Change the application program to remove this behavior, or call the reset() method first. |
| JMSCC0048 | An error occurred while trying to create the message. See the linked exception for more details. | It was not possible to create the message due to an error. | Examine the linked exception for details of the error. |
| JMSCC0049 | The property name ''XMSC_INSERT_PROPERTY'' is not a valid Java(tm) identifier. | The supplied property name does not conform to the allowed format described in the JMS specification. | Check the characters used in the property name and modify as necessary. |
| JMSCC0050 | The property name ''XMSC_INSERT_PROPERTY'' is reserved and cannot be set. | The supplied property name begins with the JMS prefix, but is not one of the supported, settable properties. | Check the property name and correct errors. |
| JMSCC0051 | The property ''XMSC_INSERT_PROPERTY'' should be set using type ''XMSC_INSERT_TYPE'', not ''XMSC_INSERT_OTHER_TYPE''. | JMS_IBM properties may only be set using a specific variable type. | Correct application code to use the required variable type when setting this JMS_IBM property. |
| JMSCC0052 | An exception occurred while serializing the object: ''XMSC_INSERT_EXCEPTION''. | It was not possible to serialize the object because of the exception. | Examine the linked exception for details of the error. |
| JMSCC0053 | An exception occurred deserializing a message, exception: ''XMSC_INSERT_EXCEPTION''. | It was not possible to deserialize the message because of the exception shown. | Examine the linked exception for details of the error. |
| JMSCC0054 | The queue browser has no messages available. | A user application requested a message from a queue browser when none was available. | Ensure the application either does not call this method when there are no messages available, or handles this exception. |
| JMSCC0055 | This queue browser is closed. | An application called a method that must not be used after the queue browser is closed. | Ensure that the queue browser is not closed before calling the method. |
| JMSCC0059 | The read buffer is null. | A null reference was passed to the StreamMessage.readBytes() method, so no data could be returned. | Pass a suitably sized buffer into the readBytes() method. |
| JMSCC0060 | The end of the message stream has been reached. | The end of the message content has been reached. This is normal if the reading application does not know how much data to expect. | No action required. |
| JMSCC0061 | The StreamMessage byte array was incompletely read. | An attempt has been made to read the next field from the stream whilst a byte array is partly read. | Ensure that the user code completes the read of any byte array before attempting to read the next field. |
| JMSCC0062 | It is not possible to return null as a character. | An attempt was made to read a StreamMessage field containing null using the readChar() method. | Avoid reading nulls using the readChar() method. |
| JMSCC0063 | The encoding is not valid for string ''JMS_IBM_Encoding''. | The supplied value does not have a known encoding. | Ensure that the application supplies a value from the defined list of encodings. |
| JMSCC0064 | An internal error occurred while writing to the data stream. | A problem has occurred with data streams used for format conversion of float and double values. | Save any generated output files and use either the WMQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. |
| JMSCC0065 | An attempt was made to read beyond the end of the message. | An attempt was made to read beyond the end of the message. This may be a normal condition if an application has been coded to read variable length data using the JMS 1.0.2 specification. | If necessary, recode the application to use the new getBodyLength() method. |
| JMSCC0066 | The UTF-8 conversion failed. | There was a problem during either reading or writing of a UTF-8 string. The most common problem is attempting to write a string longer than 65535 characters. | See the linked exception for further information. |
| JMSCC0067 | An internal error occurred. There is a problem in writing to the message. | An error was encountered whilst trying to write an item to the message. | Save any generated output files and use either the WMQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. |
| JMSCC0068 | The property ''XMSC_INSERT_PROPERTY'' must be set using a value of type ''XMSC_INSERT_TYPE'', or a type convertible to this type as per the JMS Specification. Cannot convert from given type ''XMSC_INSERT_OTHER_TYPE''. | Conversion between the two specified data types is not permitted by the JMS specification. | Set the named property using one of the permitted conversions. |
| JMSCC0069 | The property ''XMSC_INSERT_PROPERTY'' must be set using a value of type ''XMSC_INSERT_TYPE''. Cannot convert from given type ''XMSC_INSERT_OTHER_TYPE'' with value ''XMSC_INSERT_VALUE''. | An error was encountered whilst trying to set a message property. | Set the named property using one of the permitted conversions with an appropriate value. |
| JMSCC0070 | An internal error occurred. There was a problem setting the JMS message property ''XMSC_INSERT_PROPERTY'', expected type ''XMSC_INSERT_TYPE'', using an object of type ''XMSC_INSERT_OTHER_TYPE''. | An error was encountered whilst trying to set a message property. | Save any generated output files and use either the WMQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. |
| JMSCC0083 | An incorrect object of type ''XMSC_INSERT_OBJECT'' was provided. | An object was provided to the writeObject() method that was not a Java(tm) primitive wrapper type. | Correct the application to ensure that only objects of the permitted types are passed as parameters to the writeObject() method. |
| JMSCC0084 | A property of name ''XMSC_INSERT_PROPERTY'' was not set. | ||
| JMSCC0085 | A destination was not specified. | ||
| JMSCC0086 | The batch size ''XMSC_INSERT_BATCH_SIZE'' was incorrect. | ||
| JMSCC0087 | A server session pool was not specified. | ||
| JMSCC0088 | Could not obtain session from specified server session pool. | ||
| JMSCC0089 | The session ''XMSC_INSERT_SESSION'' was not valid. | ||
| JMSCC0091 | The provider factory for connection type ''XMSC_CONNECTION_TYPE'' could not be loaded. | ||
| JMSCC0092 | The connection type was expected to be ''XMSC_CONNECTION_TYPE_NAME'' but instead it actually was ''XMSC_CONNECTION_TYPE''. | ||
| JMSCC0093 | The destination was not valid. The durable subscription on a temporary destination with type ''XMSC_INSERT_TYPE'' and name ''XMSC_DESTINATION_NAME'' cannot be created. | ||
| JMSCC0094 | This connection browser is closed. | ||
| JMSCC0095 | The destination name ''XMSC_DESTINATION_NAME'' is not valid. | The destination name specified does not conform to published destination syntax. | Correct the specified destination name and try again. |
| JMSCC0097 | Bad acknowlegement mode ''XMSC_ACKNOWLEDGE_MODE''. Connection.createSession() was asked to create a non-transacted session (transacted was false) but the acknowledgement mode was not one of AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE or CLIENT_ACKNOWLEDGE. | ||
| JMSCC0098 | The message cannot be null. | Specify a non-null message. | |
| JMSCC0099 | The destination ''XMSC_DESTINATION_NAME'' is not an instance of com.ibm.msg.client.jms.JmsDestination. | Specify an instance of com.ibm.msg.client.jms.JmsDestination instead. | |
| JMSCC0100 | The subscription name cannot be null. | Specify a non-null subscription name. | |
| JMSCC0101 | The client ID cannot be null. | Specify a non-null client ID. | |
| JMSCC0102 | The property name ''XMSC_INSERT_PROPERTY'' in the message is not a valid Java(tm) identifier. | The supplied property name does not conform to the allowed format described in the JMS specification. | Check the characters used in the property name and modify as necessary. |
| JMSCC0103 | A null object was provided. | An object was provided to the writeObject() method that was null. | Correct the application to ensure that only non-null objects are passed as parameters to the writeObject() method. |
| JMSCC0105 | The conversion of the item ''XMSC_INSERT_PROPERTY'' from type ''XMSC_INSERT_TYPE'' to type ''XMSC_INSERT_OTHER_TYPE'' is not permitted. | The conversion between the two specified data types is not permitted by the JMS specification. | Retrieve the named item using one of the permitted conversions. |
| JMSCC0106 | Failed to get an XA resource. ''XMSC_INSERT_EXCEPTION''. | See the cause for more information. | |
| JMSCC0107 | Bad timeout ''XMSC_INSERT_TIMEOUT''. | The timeout must be positive or zero, measured in milliseconds. | Do not pass a negative timeout. |
| JMSCC0108 | The WebSphere MQ classes for JMS had detected a message, ready for asynchronous delivery to an application. When delivery was attempted, the message was no longer available. See the "Troubleshooting JMSCC0108 messages" topic in the WebSphere MQ V7.5 section of IBM Knowledge Center for possible causes and actions. | An internal thread within the WebSphere MQ classes for JMS had detected a message, and requested that another internal thread get the message and deliver it to an application for processing. When that thread tried to get the message, it was no longer available. | See the "Troubleshooting JMSCC0108 messages" topic in the WebSphere MQ V7.5 section of IBM Knowledge Center for more information. |
| JMSCC0109 | A message driven bean threw a runtime exception ''XMSC_INSERT_EXCEPTION''. | This may indicate a problem in the message listener. | If the runtime exception was thrown unintentionally by the message listener, use the linked exception to determine the cause of the problem. |
| JMSCC0110 | An exception ''XMSC_INSERT_EXCEPTION'' was caught while processing a message for delivery to a message driven bean. | Examine the linked exception for more information. | |
| JMSCC1026 | An exception was thrown while the user's exception listener was running. | ||
| JMSCC1027 | The exception listener failed to run. | ||
| JMSCC1069 | The operation for an XA transacted session was not valid. | The acknowledgement mode for a transacted session was not valid. Commit(), rollback(), acknowledge() and recover() are not valid operations in transacted sessions. | Do not call these method when using XA. |
| JMSCC1083 | Incorrect message batch size (must be greater than zero). | An incorrect batch size parameter was passed to createConnectionConsumer() or createDurableConnectionConsumer(). | Set a batch size greater than zero. In an application server that is JEE compliant, this may represent an error in the application server. Refer to your application server's documentation. |
| JMSCC1084 | A null server session pool has been provided. | The server session pool specified on createConnectionConsumer() or createDurableConnectionConsumer() was null. | Set an appropriate ServerSessionPool. In an application server that is JEE compliant, this may represent an error in the application server. Refer to your application server's documentation. |
| JMSCC1093 | A null parameter was passed. | An object required by this method was not correctly initialized. | Ensure that all the parameters passed to this method are correctly initialized. |
| JMSCC1094 | QuantityHint is not valid. | An attempt was made to create a connection browser with an incorrect data quantity hint. | Specify either NO_DATA, HEADER_DATA or FULL_DATA. |
| JMSCC1096 | The message reference is not valid. | An incorrectly formed message reference was passed to this method. The message reference must be an instance of JmsMessageReference. | Ensure correct message references are being used. |
| JMSCC1112 | The operation for a domain specific object was not valid. The operation ''XMSC_INSERT_METHOD'' is not valid for type ''XMSC_INSERT_TYPE''. | A JMS application attempted to perform an operation on domain specific object, but the operation is valid only for the other messaging domain. | Make sure that the JMS objects and operations used by your application are relevant for the required messaging domain. If your application uses both messaging domains, consider using domain independent objects throughout the application. |
| JMSCC3002 | The temporary queue destination ''XMSC_DESTINATION_NAME'' cannot be deleted as it is still in use. | An attempt has been made to delete a temporary destination while it is still in use by a consumer or browser. | Close all consumers and browsers which are dependent on the destination before deleting it. |
| JMSCC3003 | Incorrect use of temporary destination ''XMSC_DESTINATION_NAME''. | The use of temporary destinations by message consumers and browsers is restricted to those created using the same connection. | Modify the application to use a temporary destination created by the same connection and try again. |
| JMSCC3019 | Temporary destination has already been deleted ''XMSC_DESTINATION_NAME''. | The temporary destination has already been deleted when an attempt to use it was made. | Modify the application avoid closing the temporary desttination or use a different destination. |
| JMSCC3025 | The temporary topic destination ''XMSC_DESTINATION_NAME'' cannot be deleted as it is still in use. | An attempt has been made to delete a temporary destination while its still in use by a consumer or browser. | Close all consumers and browsers which are dependent on the destination before deleting it. |
| JMSCC3031 | A client ID cannot be set after connection has been used. | The client ID of a connection can be set only once, and only before the connection is used. | Set the client ID before using the connection. |
| JMSCC3032 | Resetting the client ID is not allowed. | The client ID of a connection can be set only once, and only before the connection is used. | Set the client ID before using the connection. |
| JMSCC3033 | The close() call within the message listener would have deadlocked. | The close() method was called from a message listener. The close() call is not allowed to return whilst the message listener is running and will therefore deadlock. | Change application to not call any close() methods from within a message listener. |
| JMSCC3034 | The exception is ignored as no exception listener is registered: ''XMSC_INSERT_EXCEPTION''. | An attempt was made to deliver an exception to the connection's exception listener but a listener has not been registered. | An exception listener must be registered with the connection to receive its exceptions. |
| JMSCC3035 | The exception is ignored as its type is outside those chosen for the exception listener: ''XMSC_INSERT_EXCEPTION''. | The exception does not fall inside the types chosen for delivery to the connection's exception listener and so has been ignored. | Review the ASYNC_EXCEPTIONS connection setting to ensure the exception filtering is set as intended. |
| JMSCC3036 | An exception has been delivered to the connection''s exception listener: ''XMSC_INSERT_EXCEPTION''. | Review the exception details for further information. | |
| JMSCC3039 | The subscription name was null or an empty string. | Durable connection consumers must have a subscription name that is not null and is not an empty string. | Pass a subscription name that is not null and is not an empty string. |
| JMSCC3040 | The attempt to modify the Connection Metadata was ignored. | Connection Metadata is read-only, properites cannot be modified. | Modify the application to not attempt to modify the Connection Metadata. |
| JMSCC3041 | The attempt to set multiple properties at once failed. The properties are ''XMSC_INSERT_PROPERTY''. | One or more of the properties failed validation so none of the changes were made. | Check the combination of properties have valid values. |
| JMSCC4001 | Distributed transactions are unavailable. | An attempt was made to use distributed transactions in an environment where they are not available. | |
| JMSCC5010 | Overriding ConnectionFactory properties from PropertyStore: XMSC_INSERT_PROPERTY_OVERRIDE_LIST | ||
| JMSCC5011 | Overriding property XMSC_OVERRIDDEN_PROPERTY: Original value = XMSC_ORIGINAL__PROPERTY_VALUE New value = XMSC_NEW_PROPERTY_VALUE | ||
| JMSCMQ0001 | WebSphere MQ call failed with compcode ''{0}'' (''{1}'') reason ''{2}'' (''{3}''). | ||
| JMSCMQ0002 | The method ''XMSC_INSERT_METHOD'' failed. | A WebSphere MQ call failed. | Please see the linked exception for more information. |
| JMSCMQ0003 | The destination ''XMSC_DESTINATION_NAME'' not understood or no longer valid. | The queue or topic might have become unavailable, the application might be using an incorrect connection for the queue or topic, or the supplied destination is not of the correct type for this method. | Check that WebSphere MQ is still running and the queue manager is available. Check that the right connection is being used for your queue or topic. |
| JMSCMQ0004 | The value ''XMSC_INSERT_VALUE'' was not valid for the property ''XMSC_INSERT_PROPERTY''. | The value of the property ''{1}'' was none of the valid values for this property. | Set the property to a valid value. |
| JMSCMQ0005 | The destination name ''XMSC_DESTINATION_NAME'' was not valid. | The destination name specified does not conform to published destination syntax. | Correct the specified destination name and try again. |
| JMSCMQ0006 | The destination is not a temporary destination cannot be deleted. | Only temporary destinations can be deleted. | |
| JMSCMQ0007 | An unknown property ''XMSC_INSERT_KEY'' with value ''XMSC_INSERT_VALUE'' was set on the destination property context. | The property ''{0}'' was not recognised - it may be a custom property. | Ensure that this is intended to be a custom property. |
| JMSCMQ0008 | WebSphere MQ classes for JMS attempts to use a data type not supported by a message or attempts to read data in the wrong type. | Wrong data types used to read message property types. | Check that the message received and the properties to be read are of the type expected. |
| JMSCMQ0009 | The end of stream has unexpectedly been reached when a stream message or bytes message was read. | The byte stream being read is shorter than the buffer supplied. This can also be caused by receiving a corrupt stream message or bytes message. | Check the length of buffer supplied. Check system event logs for more detailed information and any other reported failures. |
| JMSCMQ0017 | End of stream. | ||
| JMSCMQ0018 | A received message could not be correctly parsed. | The message with messageID = ''{0}'' and correlationID = ''{1}'' could not be correctly parsed. The last successful data read from the message was at position ''{2}'' in buffer ''{3}'' | Examine the message data and ensure that it is of the correct format to be parsed as an MQJMS Message. |
| JMSCMQ1000 | Failed to create JMS message. | The wrong message type or properties were specified when creating a base message with messageID = ''{0}'' and correlationID = ''{1}''. | Check the linked WebSphere MQ exception reason and completion code for more information and check the log file for detailed message contents. |
| JMSCMQ1006 | The value for ''XMSC_INSERT_PROPERTY'':''XMSC_INSERT_VALUE'' is not valid. | The value ''{1}'' for property ''{0}'' is not correct. | Check the linked WebSphere MQ exception reason and completion code. |
| JMSCMQ1044 | String is not a valid hexadecimal number - ''XMSC_INSERT_HEX_STRING''. | Either an attempt was made to specify a group ID or correlation ID which starts with the prefix ID but is not followed by a well-formed hexadecimal value, or an attempt was made to receive a message which contains an MQRFH2 property of type bin.hex that does not have a well-formed hexadecimal value. | Ensure that a valid hexadecimal value always follows the ID prefix when setting group ID or correlation ID values. Ensure that any MQRFH2 headers generated by non-JMS applications are well-formed. |
| JMSCMQ1046 | The character set ''CCSID'' is not supported. | An attempt was made to send or receive a map message, stream message or text message whose body is encoded using a character set not supported by the JVM. In the case of text messages, this exception might be thrown when the body of the message is first queried, rather than at receive time. | Only encode a message using a character set known to be available to the receiving application. |
| JMSCMQ1047 | The map message has an incorrect format. | A map message was received, but its MQRFH2 header information is badly formatted. | Ensure any non-JMS applications are building well-formed MQRFH2 header information for inclusion in map messages. |
| JMSCMQ1048 | The stream message has an incorrect format. | A stream message was received and is badly formatted. | Ensure any non-JMS applications are building well-formed stream messages. |
| JMSCMQ1050 | The MQRFH2 header has an incorrect format. | Received a message with a badly formed MQRFH2 header. | Ensure that any non-JMS applications building messages with MQRFH2 headers create well-formed MQRFH2 headers. |
| JMSCMQ1053 | An incorrect UTF-16 surrogate character ''XMSC_INSERT_CHARACTER'' is detected. | A UTF-16 surrogate character was encountered which is not valid as part of a topic name or MQRFH2 property. | Ensure that, when specifying UTF-16, topic names or MQRFH2 properties are well-formed. |
| JMSCMQ1054 | An incorrect XML escape sequence ''XMSC_INSERT_STRING'' is detected. | An XML escape sequence was encountered which is not valid in the MQRFH2 header of a received message. | Ensure that only valid XML escape sequences are placed into any MQRFH2 headers built by non-JMS applications. |
| JMSCMQ1055 | The property or element in the message has a datatype ''XMSC_INSERT_TYPE'' incompatible with the method used to access it. | The accessor method used to retrieved a property from a JMS message, is incompatible with the type of the property being retrieved. For example, attempting to retrieve an integer property using the getBooleanProperty() method. | Use an accessor method defined by the JMS specification as being able to retrieve property values of the required type. |
| JMSCMQ1056 | The property or element datatype ''XMSC_INSERT_TYPE'' is unsupported. | This error is caused by either attempting to set a property of a JMS message using an object which is not one of the supported types or attempting to set or receive a message whose MQRFH2 contains an element representing a property which does not have a valid type associated with it. | Ensure that when setting message properties, you use a valid JMS object type. If this exception occurs when receiving a message containing an MQRFH2 header sent by a non-JMS application, ensure that the MQRFH2 header is well-formed. |
| JMSCMQ1066 | Unsupported property name ''XMSC_INSERT_PROPERTY''. | Attempted to set a message property using either a property name which is not valid, or the name of a property which cannot have its value set. | Ensure that the property name specified conforms to the JMS specification. If the property name supplied is that of a JMS property, or a vendor specific extension, ensure that this property can be set. |
| JMSCS0001 | The properties from properties file ''{0}'' could not be loaded because of an IOException. | Check that the properties file exists and has appropriate permissions. | |
| JMSCS0002 | The call could not be completed because CommonServices has not been initialized. | CommonServices is an internal component and needs to be initialized at startup but has failed. | Check that the installation and classpath setup is correct. |
| JMSCS0003 | A CommonServices component was not found. | CommonServices is an internal component and was not found. | Check that the installation and classpath setup is correct. |
| JMSCS0004 | A Messaging Provider component was not found. | A request has been made to use a Messaging Provider that is not present in the current configuration. | Check that the JAR file containing the Messaging Provider is present on the classpath or has been registered. |
| JMSCS0005 | A component was unable to be located by the Component Manager. | A request has been made to use a Component that is not present in the current configuration. | Check that the JAR file containing the Component is present on the classpath or has been registered. |
| JMSCS0006 | An internal problem occurred. Diagnostic information for service was written to ''{0}''. Please terminate the application as the product is in an inconsistent internal state. | Save any generated output files and use either the WMQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. | |
| JMSCS0009 | System properties could not be loaded because of an AccessControlException. | The PropertyStore could not query system properties because the security policy does not allow it. | Modify the security policy to allow system properties to be read. |
| JMSCS0010 | WebSphere class for JMS common services could not locate or initialise a component due to exception ''XMSC_INSERT_EXCEPTION''. | ||
| JMSCS0020 | The class may not be serialized or deserialized as it has not been included in the whitelist ''XMSC_WHITELIST''. | ||
| JMSCS0021 | The whitelist file ''XMSC_WHITELIST'' cannot be opened | ||
| JMSCS0022 | The whitelist file ''XMSC_WHITELIST'' already exists and may not be overwritten | ||
| JMSCS0023 | The whitelist ''XMSC_WHITELIST'' has an invalid entry | ||
| JMSCS0024 | The whitelist file could not be written | ||
| JMSCS0025 | Whitelist ENFORCEMENT enabled - the whitelist file ''XMSC_WHITELIST'' is being used to validate ObjectMessage serialization and deserialization operations - the whitelist tree is ''XMSC_WHITELIST_CONTENTS'' | ||
| JMSCS0026 | WhiteList DISCOVERY enabled - The whitelist file ''XMSC_WHITELIST'' is being used to record ObjectMessage serialization and deserialization operations | ||
| JMSCS0027 | Whitelist ENFORCEMENT enabled - the whitelist ''XMSC_WHITELIST'' is being used to validate ObjectMessage serialization and deserialization operations | ||
| JMSCS0028 | WhiteList DISCOVERY requested, but the whitelist filename ''XMSC_WHITELIST'' is not a file URI | ||
| JMSCS0029 | No WhiteList functionality enabled - either the properties were not set, or the security permissions prevent them being read | ||
| JMSCS0030 | The WebSphere MQ messaging client trace mechanism does not have permission to write to the trace file ''XMSC_TRACE_FILE_NAME'' in the directory ''XMSC_TRACE_DIRECTORY_NAME'' | ||
| JMSCS0031 | An exception occurred while trying to write the trace file ''XMSC_TRACE_FILE_NAME'' in the trace directory ''XMSC_TRACE_DIRECTORY_NAME''. The exception was ''XMSC_EXCEPTION'' | ||
| JMSCS0032 | The WebSphere MQ messaging client trace mechanism could not initialize the trace file ''XMSC_TRACE_FILE_NAME'' due to the exception ''XMSC_EXCEPTION''. Trace will be written to System.Err. | ||
| JMSFMQ0001 | The connection mode ''XMSC_WMQ_CONNECTION_MODE'' is not supported for XA connections. | Not all connection modes are supported by each type of connection. XA requires a client mode connection. | Modify the connection mode to a supported value. |
| JMSFMQ0003 | The queue manager command level ''XMSC_INSERT_COMMAND_LEVEL'' did not match the requested Provider Version ''XMSC_WMQ_PROVIDER_VERSION''. | The queue manager version specified on the connection factory does not match the requested queue manager. An 'unspecified' Provider Version will attempt a Normal Mode connection. | Select a matching queue manager or modify the requested command level. |
| JMSFMQ0004 | The sharing conversations channel value ''XMSC_INSERT_VALUE'' is not supported for the requested provider version ''XMSC_WMQ_PROVIDER_VERSION''. | The value specified for the sharing conversations channel property is not supported by the requested queue manager Provider Version. An 'unspecified' Provider Version will attempt a Normal Mode connection. | Either select a Provider Version which can support the requested setting or change the sharing conversations setting to a supported value. |
| JMSFMQ0005 | The use of a client connection is not supported within the current environment. | The client connection mode is not supported in all environments. | Modify the connection mode to specify a bindings connection to a local queue manager. |
| JMSFMQ0007 | An unknown property ''XMSC_INSERT_KEY'' with value ''XMSC_INSERT_VALUE'' was set on the connection factory property context. | The property ''{0}'' was not recognised - it may be a custom property. | Ensure that this is intended to be a custom property. |
| JMSFMQ0010 | The value ''XMSC_INSERT_VALUE'' is not valid for the client configuration property ''XMSC_INSERT_NAME'', the value has been ignored. | An attempt was made to set a client configuration property outside of its valid range. | The setting must be modified to contain a valid value. Please refer to the documentation for further information. |
| JMSFMQ1006 | The value ''XMSC_INSERT_VALUE'' for property ''XMSC_INSERT_NAME'' is not valid. | The value specified for the property is not supported. | Modify the value to be within the range of accepted values. |
| JMSFMQ1007 | A log message from the Real Time Transport ''XMSC_REAL_TIME_LOG_MSG''. | The Real Time Transport logged an error. | |
| JMSFMQ1056 | The property or element datatype ''XMSC_INSERT_NAME'' is not supported. | The datatype of the given object is not accepted for the given field. | Modify the object to be of an accepted type. |
| JMSFMQ1105 | A local port ''XMSC_WMQ_LOCAL_ADDRESS'' cannot be specified for a direct connection to a broker using multicast. | A port number was specified. This is not valid for multicast. | Remove the port reference from the multicast local address setting. |
| JMSFMQ3032 | Resetting the clientID is not allowed. | The Client ID of a connection can be set only once, and only before the connection is used. | Set the Client ID before using the connection. |
| JMSFMQ3036 | Broker side message selection is only valid when using WebSphere MQ Integrator broker. | Broker version and message selection are not consistent. | Ensure the broker version (JMSC.MQJMS_BROKER_V2) has been set in the ConnectionFactory. |
| JMSFMQ3037 | Broker version and provider version concurrently set - provider version ''XMSC_WMQ_PROVIDER_VERSION'' overriding broker version ''XMSC_WMQ_BROKER_VERSION''. | Broker version and provider version must not be set concurrently. | Ensure either the broker version or the provider version has been set in the ConnectionFactory, not both. |
| JMSFMQ6115 | An exception occurred while creating the TopicConnection. | See the linked exception for further information. | |
| JMSFMQ6311 | The transport type 'DIRECT' within a transaction is not supported. | The application attempted to use a transactional method. This is not supported with a DirectIP transport type. | The application should be modified to prevent the use of transactions. |
| JMSFMQ6312 | An exception occurred in the Java(tm) MQI. | The Java(tm) MQI has thrown an exception describing the problem. | See the linked exception for further information. |
| JMSFMQ6313 | A WMQ Connection has been made of type ''XMSC_INSERT_VALUE''. | A Connection can be of either Normal Mode or Migration Mode. | If this is not the expected connection type please search the Information Center for topic jm41140_ for additional information. |
| JMSFMQ6314 | The Connection Factory supplied ProviderVersion of ''XMSC_WMQ_PROVIDER_VERSION'' has been overridden to ''XMSC_INSERT_NAME''. | The Connection Factory ProviderVersion can be overridden by the Client Configuration Property. | None; this is an information message to indicate a property has been overridden. |
| JMSFMQ6315 | ProviderVersion overriden to 6.0.0.0 as BrokerVersion set to V2 and BrokerQmgr present in ConnectionFactory. | The Connection Factory ProviderVersion has been changed based on other properties in the Connection Factory. | None; this is an information message to indicate a property has been overridden. |
| JMSFMQ6316 | QueueManager Publish Subscribe Mode is ''XMSC_INSERT_TYPE'' mode, ''XMSC_INSERT_OTHER_TYPE'' is therefore required for Publish Subscribe function. | Based on the QueueManager Published Subscribe mode a decision has been made on use of either Normal or Migration mode. | None; this is an information messages. Please search the Information Center for topic jm41140_ for additional information. |
| JMSFMQ6317 | Unable to open the BrokerControlQ ''XMSC_INSERT_TYPE'' mode, Normal Mode is therefore required for Publish Subscribe function. | Based on the QueueManager Published Subscribe mode a decision has been made on use of either Normal or Migration mode. | None; this is an information messages. Please search the Information Center for topic jm41140_ for additional information. |
| JMSFMQ6318 | Unable to integrate with WMQ Server Trace Control ''Exception'' . | It has not been possible to connect to the WMQ Server Trace. | Check the classpath to ensure that the com.ibm.mq.commonservices.jar is present. |
| JMSMQ0000 | Method ''XMSC_INSERT_NAME'' has been invoked at an illegal or inappropriate time, or the provider is not in an appropriate state for the requested operation. | The normal reason for this exception is that the SSL certificate stores have not been defined. ''{0}'' identifies the method that has caused the problem. | |
| JMSMQ0003 | The destination is not understood or no longer valid. | The queue or topic might have become unavailable, the application might be using an incorrect connection for the queue or topic, or the supplied destination is not of the correct type for this method. | Check that WebSphere MQ is still running and the queue manager is available. Check that the right connection is being used for your queue or topic. |
| JMSMQ0012 | The version cannot be changed once the connection factory or destination has been created. | Specify the correct version when creating the connection factory or destination. | |
| JMSMQ1006 | Incorrect value for ''XMSC_INSERT_PROPERTY'': ''XMSC_INSERT_VALUE''. | The value given for the property is outside its range of valid values. | Check the value that has been provided |
| JMSMQ1046 | The character set ''{0}'' is not supported. | ||
| JMSMQ1096 | Incorrect message reference. | An incorrectly formed MessageReference was passed to this method. The message reference must be an instance of MQMessageReference. | Ensure correct MessageReferences are being used. |
| JMSMQ1112 | The operation for a domain specific object was not valid. The operation ''XMSC_INSERT_METHOD'' is not valid for type ''XMSC_INSERT_TYPE''. | A JMS application attempted to perform an operation on domain specific object, but the operation is valid only for the other messaging domain. | Make sure that the JMS objects and operations used by your application are relevant for the required messaging domain. If your application uses both messaging domains, consider using domain independent objects throughout the application. |
| JMSMQ1113 | The destination does not have a name set. | An attempt was made to use a MQQueue or MQTopic that was created with the default constructor. A name should have then been set before the queue was used. | After creation set a name on the MQQueue or MQTopic. |
| JMSMQ1114 | The method ''XMSC_INSERT_METHOD'' is an internal method and must not be called. | An attempt was made to use a method that is for internal use only. This method is not part of the published API and must not be used. | Remove use of this method from the application. Please contact IBM Service for futher information. |
| JMSMQ1115 | No components were found. | No components were located by the Component Manager. | Check that the installation and classpath setup is correct. |
| JMSMQ1120 | The Cleanup function is not supported on the requested provider version ''XMSC_WMQ_PROVIDER_VERSION''. | The operations performed by cleanup are not required for the requested provider version. | Make sure that the supplied provider version is correct. |
| JMSMQ1121 | A ConnectionMetaData object was created using the constructor rather than obtained from a connection. | ConnectionMetaData objects should be obtained from the connection not created directly. The version information returned therefore might be inaccurate. | Obtain the ConnectionMetaData from a connection or use the version API to get static version information. |
| JMSMQ1123 | JNI library not located, this is expected for a client installation. | The JNI libraries (mqjbnd) can not be found. This is expected for a MQ client installation | If this is MQ client installation then this message is expected. If this is an MQ server installation then investigate why the JNI libraries (mqjbnd) can not be found or contact IBM Support for further investigation. |
| JMSMQ3043 | Invalid Level for repeating Cleanup. | ||
| JMSMQ5115 | Failed to set properties on the queue connection factory | ||
| JMSWMQ0002 | Extra diagnostics provided by MQSTAT: compcode ''{0}'' reason ''{1}'' object name ''{2}'' resolved object name ''{3}'' object type ''{4}'' queue manager name ''{5}'' resolved queue manager name ''{6}'' put failure count ''{7}'' put success count ''{8}'' put warning count ''{9}''. | ||
| JMSWMQ0003 | The queue manager command level ''XMSC_INSERT_COMMAND_LEVEL'' did not match the requested provider version ''XMSC_WMQ_PROVIDER_VERSION''. | ||
| JMSWMQ0006 | WebSphere MQ classes for JMS attempts to use a data type not supported by a message or attempts to read data in the wrong type. | Wrong data types used to read message property types. | Check that the message received and the properties to be read are of the type expected. |
| JMSWMQ0007 | WebSphere MQ classes for JMS attempts to use a data type not supported by a message or attempts to read data in the wrong type. | Wrong data types used to read message property types. | Check that the message received and the properties to be read are of the type expected. |
| JMSWMQ0008 | WebSphere MQ classes for JMS attempts to use a data type not supported by a message or attempts to write data in the wrong type. | Wrong data types used to write message property types. | Check that the message received and the properties to be written are of the type expected. |
| JMSWMQ0009 | WebSphere MQ classes for JMS is unable to allocate the resources required for a method. | Machine resources might be overloaded, the linked exception might give further information. | Check system resources and load. |
| JMSWMQ0010 | Failed to get the command level of the queue manager ''XMSC_INSERT_QUEUE_MANAGER''. | Please see the linked exception for more information. | |
| JMSWMQ0011 | Failed to initialise the Java(tm) interface to the MQI ''XMSC_INSERT_EXCEPTION''. | Please see the linked exception for more information. | |
| JMSWMQ0017 | End of stream. | ||
| JMSWMQ0018 | Failed to connect to queue manager ''XMSC_INSERT_QUEUE_MANAGER'' with connection mode ''XMSC_WMQ_CONNECTION_MODE'' and host name ''XMSC_WMQ_HOST_NAME''. | Check the queue manager is started and if running in client mode, check there is a listener running. Please see the linked exception for more information. | |
| JMSWMQ0019 | Failed to disconnect from queue manager ''XMSC_INSERT_QUEUE_MANAGER'' using connection mode ''XMSC_WMQ_CONNECTION_MODE'' and host name ''XMSC_WMQ_HOST_NAME''. | Please see the linked exception for more information. | |
| JMSWMQ0020 | Failed to register callback using MQCB for destination ''XMSC_DESTINATION_NAME''. | Please see the linked exception for more information. | |
| JMSWMQ0021 | Failed to deregister callback using MQCB for destination ''XMSC_DESTINATION_NAME''. | Please see the linked exception for more information. | |
| JMSWMQ0022 | Failed to start consuming messages using MQCTL for destination ''XMSC_DESTINATION_NAME''. | Please see the linked exception for more information. | |
| JMSWMQ0023 | Failed to suspend consuming messages using MQCTL for destination ''XMSC_DESTINATION_NAME''. | Please see the linked exception for more information. | |
| JMSWMQ0024 | Failed to resume consuming messages using MQCTL for destination ''XMSC_DESTINATION_NAME''. | Please see the linked exception for more information. | |
| JMSWMQ0025 | Failed to unsubscribe from topic ''XMSC_DESTINATION_NAME'' using MQCLOSE. | There might have been a problem removing the subscription because it is being used by a message consumer. | Make sure any message consumers using this subscription are closed before unsubscribing. Please see the linked exception for more information. |
| JMSWMQ0026 | Failed to subscribe to topic ''XMSC_DESTINATION_NAME'' using MQSUB. | There may have been a problem creating the subscription due to it being used by another message consumer. | Make sure any message consumers using this subscription are closed before trying to create a new subscription under the same name. Please see the linked exception for more information. |
| JMSWMQ0027 | The message contains a bad encoding ''encoding''. | A message with a badly formed header has been received. The encoding must either be normal or reversed. | Ensure that any non-JMS applications building messages create well-formed headers. |
| JMSWMQ0028 | At least one asynchronous put message failed or gave a warning. | When a message is put asynchronously, any problems are not reported as exceptions thrown from the send() method. Instead they are passed to the exception listener, if one is defined. The exception listener is driven at syncpoint for transacted sessions, or every SEND_CHECK_COUNT asynchronous puts for non-transacted sessions. | Please see the linked exception for more information on the failures and/or warnings. |
| JMSWMQ0029 | Failed to send a report message to replyTo queue ''XMSC_DESTINATION_NAME''. | Please see the linked exception for more information on the failures and/or warnings. | |
| JMSWMQ0030 | ''XMSC_INSERT_METHOD'' failed for destination ''XMSC_DESTINATION_NAME'' when handling a poison message. | When requeuing a poison message, ''{0}'' failed when called for the destination ''{1}''. | Please see the linked exception for more information on the failures and/or warnings. |
| JMSWMQ0031 | ''XMSC_INSERT_METHOD'' failed for the queue manager when handling a poison message. | When requeuing a poison message, ''{0}'' failed when attempting to inquire about the queue manager. | Please see the linked exception for more information on the failures and/or warnings. |
| JMSWMQ0032 | There is no dead letter queue defined. | WebSphere MQ classes for JMS attempted to put a poisonous message to the dead letter queue because it could not be routed to the backout retry queue. This failed because there was no dead letter queue defined to the queue manager. | Define a dead letter queue. |
| JMSWMQ0033 | The backout requeue name for destination ''XMSC_DESTINATION_NAME'' cannot be converted from the queue manager''s coded character set id ''CCSID''. | Check the backout requeue name and the queue manager's coded character set id. | |
| JMSWMQ0034 | The dead letter queue name cannot be converted from the queue manager''s coded character set id ''CCSID''. | Check the dead letter queue name and the queue manager's coded character set id. | |
| JMSWMQ0035 | Message ''XMSC_INSERT_MESSAGE_ID'', could not be moved to dead letter queue ''XMSC_INSERT_DESTINATION_NAME'' because of exception ''XMSC_INSERT_EXCEPTION'', it will be returned to the source queue. | When running in WebSphere MQ messaging provider normal mode, a message was detected that could not be processed. An attempt was made to move the message to the dead letter queue, but this has failed. | Please see the linked exception for more information on the failures and/or warnings. |
| JMSWMQ0036 | Application Server Facilities caught exception ''XMSC_INSERT_EXCEPTION''. | The WebSphere MQ classes for JMS connection browser caught an exception. | |
| JMSWMQ0037 | A poison message could not be handled due to exception ''XMSC_INSERT_EXCEPTION''. | The WebSphere MQ classes for JMS message listener caught an exception. | |
| JMSWMQ1006 | The value for ''XMSC_INSERT_PROPERTY'':''XMSC_INSERT_VALUE'' is not valid. | The value ''{1}'' for property ''{0}'' is not correct. | Check the linked WebSphere MQ exception reason and completion code. |
| JMSWMQ1017 | non-local MQ queue ''XMSC_DESTINATION_NAME'' not valid for receiving or browsing. | The MQ queue is not able to be opened, as it is not local to the connected Queue Manager. | Connect to the Queue Manager for which this MQ Queue resides locally. |
| JMSWMQ1029 | Property name is null. | The itemExists() method of the map message was invoked with a null item name, or a null name string was used as an argument to a method which retrieves property values by name from a JMS message. | Ensure that the name strings indicated do not have null values. |
| JMSWMQ1044 | String is not a valid hexadecimal number - ''XMSC_INSERT_HEX_STRING''. | Either an attempt was made to specify a group ID or correlation ID which starts with the prefix ID but is not followed by a well-formed hexadecimal value, or an attempt was made to receive a message which contains an MQRFH2 property of type bin.hex that does not have a well-formed hexadecimal value. | Ensure that a valid hexadecimal value always follows the ID prefix when setting group ID or correlation ID values. Ensure that any MQRFH2 headers generated by non-JMS applications are well-formed. |
| JMSWMQ1046 | The character set ''CCSID'' is not supported. | An attempt was made to send or receive a map message, stream message or text message whose body is encoded using a character set not supported by the JVM. In the case of text messages, this exception might be thrown when the body of the message is first queried, rather than at receive time. | Only encode a message using a character set known to be available to the receiving application. |
| JMSWMQ1055 | The property or element in the message has a datatype ''XMSC_INSERT_TYPE'' incompatible with the method used to access it. | The accessor method used to retrieved a property from a JMS message, is incompatible with the type of the property being retrieved. For example, attempting to retrieve an integer property using the getBooleanProperty() method. | Use an accessor method defined by the JMS specification as being able to retrieve property values of the required type. |
| JMSWMQ1059 | Fatal error - UTF-8 not supported. | The Java(tm) runtime environment you are using does not support the UTF-8 character encoding. JMS requires support for this encoding to perform some operations. | Consult the documentation and or provider of your Java(tm) runtime environment to determine how to obtain support for the UTF-8 character encoding. |
| JMSWMQ1067 | The timeout ''XMSC_INSERT_TIMEOUT'' not valid for WebSphere MQ classes for JMS. | An attempt was made to invoke the receive method on either a queue receiver or topic subscriber method, specifying a long timeout value which is not valid. | Ensure the timeout value specified is not negative and not greater than the value of Integer.MAX_VALUE. |
| JMSWMQ1068 | Failed to obtain the XA resource. | WebSphere MQ classes for JMS failed to create an XA resource due to an error. | See the linked XAException for more information. |
| JMSWMQ1079 | Unable to write a message to dead letter queue. | WebSphere MQ classes for JMS failed to requeue a message to the dead letter queue. | Use the linked exception to determine the cause of this error. If there is no linked exception, check that the queue manager has a defined a dead letter queue. Once WebSphere MQ classes for JMS has sent a message to the dead letter queue, the reason code stored in the message's MQDLH can be used to determine why the message was sent there. |
| JMSWMQ1080 | No Backout-Requeue queue defined. | ||
| JMSWMQ1096 | A message reference was formed incorrectly. | ||
| JMSWMQ1107 | A problem with this connection has occurred. | An error has occurred with the WebSphere MQ JMS connection. | Use the linked exception to determine the cause of this error. |
| JMSWMQ1116 | Message ''XMSC_INSERT_MESSAGE_ID'', which was on the queue ''XMSC_INSERT_DESTINATION_NAME'' has been moved to the dead letter queue on queue manager ''XMSC_INSERT_QUEUE_MANAGER_NAME'' | When running in WebSphere MQ messaging provider normal mode, a message was detected that could not be processed. Because the Report field in the MQMD for this message contained the option MQRO_DEAD_LETTER_Q, the message was moved to the dead letter queue. | Look at the dead letter header on the message on the dead letter queue to determine why the message could not be processed. |
| JMSWMQ1117 | Message ''XMSC_INSERT_MESSAGE_ID'', which was on the queue ''XMSC_INSERT_DESTINATION_NAME'' on queue manager ''XMSC_INSERT_QUEUE_MANAGER_NAME'', cannot be processed and has been discarded. | When running in WebSphere MQ messaging provider normal mode, a message was detected that could not be processed. Because the Report field in the MQMD for this message contained the option MQRO_DISCARD_MSG, the message was discarded. | Modify the applications that are putting messages to the queue specified, so that the Report field in the MQMD for the message contains the option MQRO_DEAD_LETTER_Q. This will ensure that any subsequent messages that cannot be processed will be moved to the dead letter queue rather than being discarded. Messages on the dead letter queue will have a dead letter header, containing information about why the message could not be processed. |
| JMSWMQ1118 | The queue ''XMSC_INSERT_DESTINATION_NAME'' that was previously inhibited for get has been re-enabled for get as the WebSphere MQ queue manager has responded with reason code ''2494'' (''MQRC_GET_ENABLED'') | A queue that a consumer is connected to has now been made available to get a message from. | None. This message is for information only. |
| JMSWMQ1119 | The queue ''XMSC_INSERT_DESTINATION_NAME'' is currently inhibited for get requests as the WebSphere MQ queue manager has responded with reason code ''2016'' (''MQRC_GET_INHIBITED''). | A queue that a consumer is connected to is now inhibited from any MQGET requests. | Wait until the WebSphere MQ Administrator has re-enabled the queue for MQGET requests. |
| JMSWMQ1120 | Message ''XMSC_INSERT_MESSAGE_ID'', could not be moved to backout queue ''XMSC_INSERT_DESTINATION_NAME'' for reason ''XMSC_INSERT_REASON'', it will be moved to the dead letter queue or discarded. | When running in WebSphere MQ messaging provider normal mode, a message was detected that could not be processed. An attempt was made to move the message to the backout queue, but this has failed. | Check the reason code in this message to determine why this action failed and take appropriate steps to correct the error. |
| JMSWMQ2000 | Failed to close queue ''XMSC_DESTINATION_NAME''. | JMS attempted to close a WebSphere MQ destination, but encountered an error. The destination might already be closed, or another thread may be performing an MQGET while close() is called. | Use the linked exception to determine the cause of this error. You may be able to perform the close() later. |
| JMSWMQ2001 | Failed to close destination ''XMSC_DESTINATION_NAME'', using a read ahead close policy. | WebSphere MQ classes for JMS attempted to close a WebSphere MQ destination, but encountered an error. The close call has timed out when trying to deliver all messages on the read ahead queue. | Check that your message listener is not looping. You may be able to perform the close() later. |
| JMSWMQ2002 | Failed to get a message from destination ''XMSC_DESTINATION_NAME''. | WebSphere MQ classes for JMS attempted to perform an MQGET; however WebSphere MQ reported an error. | Use the linked exception to determine the cause of this error. |
| JMSWMQ2003 | Failed to close topic ''XMSC_DESTINATION_NAME''. | JMS attempted to close a WebSphere MQ destination, but encountered an error. The destination might already be closed, or another thread may be performing an MQGET while close() is called. | Use the linked exception to determine the cause of this error. You may be able to perform the close() later. |
| JMSWMQ2006 | Failed to open MQ topic ''XMSC_DESTINATION_NAME''. | JMS attempted to perform an MQOPEN, but WebSphere MQ reported an error. | Use the linked exception to determine the cause of this error. Check that the specified topic and queue manager are defined correctly. |
| JMSWMQ2007 | Failed to send a message to destination ''XMSC_DESTINATION_NAME''. | JMS attempted to perform an MQPUT or MQPUT1; however WebSphere MQ reported an error. | Use the linked exception to determine the cause of this error. |
| JMSWMQ2008 | Failed to open MQ queue ''XMSC_DESTINATION_NAME''. | JMS attempted to perform an MQOPEN, but WebSphere MQ reported an error. | Use the linked exception to determine the cause of this error. Check that the specified queue and queue manager are defined correctly. |
| JMSWMQ2010 | The destination for NPMCLASS HIGH persistent messaging ''XMSC_DESTINATION_NAME'' was not valid. | The destination specified does not support NPMCLASS HIGH persistent messaging. | Use JMS administration tool to enable NPMCLASS HIGH persistent messaging for this destination. |
| JMSWMQ2011 | Failed to open durable subscription ''XMSC_INSERT_OBJECT'' for destination ''XMSC_DESTINATION_NAME''. | Jms attempted to create a durable subscription, but the chosen subscription name was already in use within the JVM. | Use a different subscription name for this durable subscriber, or run this subscriber in another JVM. |
| JMSWMQ2012 | XACLOSE failed. | Closing the XA resource failed, while closing the XA session. | See linked XAException for more details. |
| JMSWMQ2013 | The security authentication was not valid that was supplied for QueueManager ''XMSC_INSERT_QUEUE_MANAGER'' with connection mode ''XMSC_WMQ_CONNECTION_MODE'' and host name ''XMSC_WMQ_HOST_NAME''. | Please check if the supplied username and password are correct on the QueueManager to which you are connecting. | |
| JMSWMQ2014 | MQ delivered an asynchronous event with completion code ''{0}'', and reason ''{1}''. | ||
| JMSWMQ2016 | Failed to register ExceptionListener for Connection. | The MQCB call to register this ExceptionListener failed. | Use the linked exception to determine the cause of this error. |
| JMSWMQ2017 | Failed to deregister ExceptionListener for Connection. | The MQCB call to deregister this ExceptionListener failed. | Use the linked exception to determine the cause of this error. |
| JMSWMQ2018 | Exception ignored as no exception listener is registered: ''XMSC_INSERT_EXCEPTION''. | An attempt was made to deliver an exception to the connection's exception listener but a listener has not been registered. | An exception listener must be registered with the connection to receive its exceptions. |
| JMSWMQ2019 | Unexpected completion code ''XMSC_INSERT_COMP_CODE'', reason code ''XMSC_INSERT_REASON'' returned from method ''XMSC_INSERT_METHOD''. | The reason code was not expected, but has not been returned to the application. | If the application is experiencing failures, the reason code logged should be examined as a means to provide further information into the failures. |
| JMSWMQ2020 | Failed to connect to queue manager ''XMSC_INSERT_QUEUE_MANAGER'' with connection mode ''XMSC_WMQ_CONNECTION_MODE'' and supplied CCDT URL ''XMSC_WMQ_CCDTURL'', see linked exception for more information. | Check the queue manager is started and if running in client mode, check there is a listener running. Please see the linked exception for more information. | |
| JMSWMQ2021 | The security authentication was not valid that was supplied for QueueManager ''XMSC_INSERT_QUEUE_MANAGER'' with connection mode ''XMSC_WMQ_CONNECTION_MODE'' and supplied CCDT URL ''XMSC_WMQ_CCDTURL'', see linked exception for more information. | Please check if the supplied username and password are correct on the QueueManager to which you are connecting. | |
| JMSWMQ2022 | Cannot create a Message Producer or Message Consumer with a Model Queue ''XMSC_DESTINATION_NAME'', as a Destination. | The Message Producer or Message Consumer was unable to open the Destination as it was a Model Queue. | Change the Message Producer or Message Consumer to use a different Destination Queue name other than a Model Queue. |
| JMSXY02 | Security Exception XY. | ||
| MQJCA000 | This is an internal error. A linked exception or diagnostic trace might provide additional information. | ||
| MQJCA0000 | An unknown error ''JCA_NLS_MESSAGE_ID'' occurred. | The resource adapter failed to map an internal reason code to an error message. | |
| MQJCA0001 | An exception occurred in the JMS layer. See the linked exception for details. | A call to WebSphere MQ classes for JMS caused an exception to be thrown. | See the linked exception for details of the failure. |
| MQJCA0002 | An exception occurred in the WebSphere MQ layer. See the linked exception for details. | A call to WebSphere MQ classes for Java(tm) caused an exception to be thrown. | See the linked exception for details of the failure. |
| MQJCA0003 | A JNDI naming exception was thrown. See the linked exception for details. | An attempt to look up a JMS destination in the JNDI namespace failed. Either the namespace cannot be accessed, or a destination with the supplied name is not bound in the namespace. | See the linked exception for details of the failure. Check that the JNDI namespace is available, that a destination with the correct name is bound in the JNDI namespace, and that the value of the property called destination is correctly defined. |
| MQJCA1001 | The MDB cannot be deployed. Inbound messaging is unavailable. | An attempt was made to deploy a MessageEndpoint object when inbound messaging was not available. | Find the earlier exception that indicates why inbound messaging is not available. Use the information to enable inbound messaging. |
| MQJCA1002 | An unknown ActivationSpec implementation supplied to the ResourceAdapter. | The application server attempted to use the WebSphere MQ resource adapter to deploy an ActivationSpec object that is not a WebSphere MQ ActivationSpec object. | This is an application server error. For information about how to diagnose and correct the error, see the documentation for the application server. |
| MQJCA1003 | The message endpoint has no onMessage() method. Deployment failed. | The application server attempted to use the WebSphere MQ resource adapter to deploy a message endpoint that does not implement the JMS MessageListener interface. | This is an application server error. For information about how to diagnose and correct the error, see the documentation for the application server. |
| MQJCA1004 | Distributed transactions are unavailable. | An attempt was made to use distributed transactions in an environment where they are not available. | Make sure that the WebSphere MQ extended transactional client is installed if required, or use a bindings connection. |
| MQJCA1005 | The JCA classes cannot be loaded. Deployment failed. | The JCA classes were not found in the class path. | Make sure that the application server can find the necessary JCA JAR files in the class path. |
| MQJCA1006 | An incorrect version of the JCA classes was found. Deployment failed. | The JCA classes were found in the class path but were not the correct version. | This error can occur if the application server finds connector.jar in the class path. This JAR file is required by WebSphere MQ classes for JMS in a J2SE environment, but is not required in a J2EE 1.4 environment. |
| MQJCA1007 | The WebSphere MQ classes for JMS cannot be loaded. Deployment failed. | The WebSphere MQ classes for JMS were not found in the class path. | These classes are included in the RAR file of the WebSphere MQ resource adapter. Make sure that the application server can find the classes. |
| MQJCA1008 | An incorrect version of the WebSphere MQ classes for JMS was found. Deployment failed. | The WebSphere MQ classes for JMS were found in the class path but were not the correct version. | This error can occur if the application server finds an earlier version of the WebSphere MQ classes for JMS in the class path. The error can also occur if you do not configure WebSphere Application Server to use the correct version of the WebSphere MQ classes for JMS. |
| MQJCA1011 | Failed to allocate a JMS connection. | An internal error caused an attempt to allocate a connection to fail. | See the linked exception for details of the failure. |
| MQJCA1012 | Failed to create a JMS connection factory. | A JCA ManagedConnectionFactory object was not able to create a WebSphere MQ classes for JMS ConnectionFactory object. | Check the properties of the ConnectionFactory object. |
| MQJCA1013 | Failed to obtain an XAResource object. | An attempt to access the XAResource object of an XASession object failed. | This is an internal error. A linked exception or diagnostic trace might provide additional information. |
| MQJCA1014 | Transaction begin failed. | An attempt to begin a transaction failed. | This is an internal error. A linked exception or diagnostic trace might provide additional information. |
| MQJCA1015 | Transaction commit failed. | An attempt to commit a transaction failed. | This is an internal error. A linked exception or diagnostic trace might provide additional information. |
| MQJCA1016 | Transaction rollback failed. | An attempt to roll back a transaction failed. | This is an internal error. A linked exception or diagnostic trace might provide additional information. |
| MQJCA1018 | Only one session per connection is allowed. | The application attempted to create more than one JMS session on the same JMS connection. This exception occurs only if the application is running in a managed environment. | Modify the application so that it creates only one JMS session on a JMS connection. |
| MQJCA1019 | The connection is closed. | The application attempted to use a JMS connection after it had closed the connection. | Modify the application so that it closes the JMS connection only after it has finished using the connection. |
| MQJCA1020 | The session is closed. | The application attempted to use a JMS session after it had closed the session. | Modify the application so that it closes the JMS session only after it has finished using the session. |
| MQJCA1021 | The message producer is closed. | The application attempted to use a JMS message producer after it had closed the message producer. | Modify the application so that it closes the JMS message producer only after it has finished using the message producer. |
| MQJCA1022 | The message consumer is closed. | The application attempted to use a JMS message consumer after it had closed the message consumer. | Modify the application so that it closes the JMS message consumer only after it has finished using the message consumer. |
| MQJCA1023 | Failed to allocate a JMS session. | An attempt to create a JMS session failed. | This is an internal error. A linked exception or diagnostic trace might provide additional information. |
| MQJCA1024 | The session must not have a message listener. | An application attempted to set a message listener for a JMS session. | Modify the application so that it does not use a message listener. |
| MQJCA1025 | The message consumer must not have a message listener. | An application attempted to set a message listener for a JMS message consumer. This exception occurs only if the application is running in a managed environment. | Modify the application so that it does use a message listener. |
| MQJCA1026 | An operation on a domain specific object was not valid. | A JMS application attempted to perform an operation on a domain specific object, but the operation is valid only on cross domain objects or in the other messaging domain. | Make sure that the JMS objects used by your application are relevant to the required messaging domain. |
| MQJCA1028 | Re-authentication is not supported. | The application server attempted to re-authenticate a JMS connection, but the WebSphere MQ resource adapter does not support re-authentication. | In the supplied ra.xml file, the property called reauthentication-support has the value false. Make sure that you have not changed the value of this property. If the property still has the value false, then this error is an application server error. |
| MQJCA1029 | Could not instantiate SSLSocketFactory. See the linked exception for details. | An attempt to instantiate a user-defined SSLSocketFactory failed. | Check the linked exception. Make sure the specified class name is correct, and the socket factory can be found on the class path. |
| MQJCA1030 | The class ''JCA_SSL_SOCKET_FACTORY'' does not implement javax.net.ssl.SSLSocketFactory. | The sslSocketFactory property defines a class that does not implement javax.net.ssl.SSLSocketFactory. | Ensure that the class defined in the sslSocketFactory implements javax.net.ssl.SSLSocketFactory. |
| MQJCA1031 | The method ''JCA_METHOD_NAME'' can only be called in the application client container. | The application was not running in the application client container when this method was called. | Ensure that the application runs in the application client container, or modify the application to avoid this method call. This JEE restriction may be circumvented by setting the Java system property "com.ibm.mq.connector.performJavaEEContainerChecks" to the value "false". |
| MQJCA2002 | destination property must be defined. | The ActivationSpec property called destination is not defined. | Define the property called destination. |
| MQJCA2003 | destinationType property must be javax.jms.Queue or javax.jms.Topic. | The destinationType property of an ActivationSpec object has a value that is not valid. | Set the value of the destinationType property to javax.jms.Queue or javax.jms.Topic. |
| MQJCA2004 | subscriptionName property must be defined for durable subscriptions. | An attempt was made to use a durable subscription, but the subscriptionName property is not defined. | Define the subscriptionName property. |
| MQJCA2005 | destinationType property must be javax.jms.Topic for durable subscriptions. | An attempt was made to use durable subscriptions, but the value of the destinationType property is javax.jms.Queue. | Set the value of the destinationType property to javax.jms.Topic. |
| MQJCA2006 | brokerCCDurSubQueue must be defined for durable subscriptions. | An attempt was made to use durable subscriptions, but the brokerCCDurSubQueue property is not defined. | Define the brokerCCDurSubQueue property. |
| MQJCA2007 | Non-ASF mode only supported in WebSphere Application Server. | The nonASFTimeout property was set to enable non-ASF mode, but it is not supported in the current environment. | nonASFTimeout must not be defined unless the resource adapter is running on WebSphere Application Server. |
| MQJCA3001 | Value ''JCA_CONFIG_VALUE'' for the property ''JCA_CONFIG_PROPERTY'' is not valid. | A property of an ActivationSpec or ManagedConnectionFactory object has a value that is not valid. | Supply a valid value for the property. |
| MQJCA3002 | Must specify either channel or ccdtURL in client mode. | The transportType property was set to CLIENT but no channel or ccdtURL property was defined. | Define the channel or ccdtURL property. |
| MQJCA3003 | Must not specify both channel and ccdtURL in client mode. | The transportType property was set to CLIENT and both the channel and ccdtURL properties were defined. | Define either the channel or the ccdtURL property, but not both. |
| MQJCA3004 | The property called channel must be set if the transportType property is set to BINDINGS_THEN_CLIENT. | The transportType property was set to BINDINGS_THEN_CLIENT but no property called channel was defined. | Define the property called channel. |
| MQJCA3005 | The property called ccdtURL must not be set if the transportType property is set to BINDINGS_THEN_CLIENT. | The transportType property was set to BINDINGS_THEN_CLIENT but property called ccdtURL was also defined. | Do not define the property called ccdtURL. |
| MQJCA4000 | An unknown warning occurred. | The resource adapter failed to map an internal reason code to a warning message. | This is an internal error. |
| MQJCA4001 | Unknown exception message ID: ''JCA_NLS_MESSAGE_ID''. | The exception builder was asked to build an exception but does not understand the requested type. | This is an internal error. |
| MQJCA4002 | Failed to find javax.jms.MessageListener class. Inbound messaging unavailable. Check the class path. | The javax.jms.MessageListener class was not found in the class path. Inbound messaging is not available, although outbound messaging might still work. | A problem with the class path has prevented inbound messaging from starting. Check the class path. |
| MQJCA4003 | A recoverable exception occurred in the JMS layer: ''JCA_JMS_EXCEPTION''. | A call to a JMS method threw an exception, but this failure does not directly affect the operation of the resource adapter. | Investigate the cause of the error. The exception might indicate configuration problems, or more serious issues with the resource adapter or WebSphere MQ queue manager. |
| MQJCA4004 | Message delivery to an MDB ''JCA_ENDPOINT'' failed with exception: ''JCA_JMS_EXCEPTION''. | An attempt to deliver a message to a Message Endpoint failed. The message has been rolled back onto the queue. | You can ignore a single warning if a subsequent attempt to deliver the message is successful. Repeated warnings might indicate problems with the resource adapter or the WebSphere MQ queue manager, or that a corrupt message is on the queue. |
| MQJCA4006 | Could not parse ''JCA_CONFIG_PROPERTY'' : ''JCA_CONFIG_VALUE'' using default ''JCA_CONFIG_DEFAULT''. | A property of an ActivationSpec or ManagedConnectionFactory object has a value that could not be parsed. | Supply a valid value for the property. |
| MQJCA4007 | Could not set property ''JCA_CONFIG_PROPERTY'' to ''JCA_CONFIG_VALUE''. | A property of an ActivationSpec or ManagedConnectionFactory could not be set to the supplied value. | Check that the property can be set and the supplied value is allowed. |
| MQJCA4008 | Could not process properties string: ''JCA_PROPERTY_VALUE''. | A string of property names and values to be defined on an ActivationSpec or ManagedConnectionFactory object could not be processed. | Check that the property names and values are correct, and the format of the string is valid. |
| MQJCA4009 | Could not process sslSocketFactory property: ''JCA_PROPERTY_VALUE''. | The sslSocketFactory property to be defined on an ActivationSpec or ManagedConnectionFactory object could not be processed. | Check that the format of the string is valid. |
| MQJCA4011 | An exception was thrown by ManagedConnection.destroy(). | An exception was thrown while a managed connection was closing. | The error does not affect the operation of the resource adapter because the managed connection was no longer being used. However, the error might indicate configuration problems, or more serious issues with the resource adapter or WebSphere MQ queue manager. |
| MQJCA4013 | A connection to a queue manager failed for activationSpec ''JCA_ENDPOINT''. Check the queue manager error logs for details. | A connection to a WebSphere MQ queue manager was broken. | If the reconnectionRetryCount property is not zero, the resource adapter attempts to reconnect to the queue manager. Until the connection is restarted, the delivery of messages to any MDBs supplied by the connection is suspended. |
| MQJCA4014 | Failed to reconnect one or more MDBs after a connection failure. | The connection supplying one or more MDBs failed, and the resource adapter was not able to reconnect within the number of attempts specified by the reconnectionRetryCount property. | Make sure that the WebSphere MQ queue manager is running, and that any other required components such as a listener are also running. Examine the application server logs to determine which MDBs have failed and restart the MDBs manually. |
| MQJCA4015 | The ServerSessionPool scavenger thread shut down due to a runtime exception. | The ServerSessionPool scavenger thread encountered an exception that caused it to shut down. Unused sessions will not be closed due to inactivity. | This is an internal error. Diagnostic trace might provide additional information. |
| MQJCA4016 | Unregistered connection handle being closed: ''JCA_CONNECTION_HANDLE''. | A connection closed event was received, but the resource adapter could not associate it with a known connection handle. | This is an internal error. Diagnostic trace might provide additional information. |
| MQJCA4017 | Ignoring supplied logWriter. | The application server tried to set a logWriter on a ManagedConnection, but the resource adapter has been configured to not use a supplied logWriter. | If you do not wish to use the application server logWriter, ignore this warning. Otherwise ensure that the logWriterEnabled property is set to true. |
| MQJCA4018 | MessageEndpoint afterDelivery() call failed with: ''JCA_JMS_EXCEPTION''. | The resource adapter attempted to call afterDelivery to end a transaction, but this call failed unexpectedly. | This is an internal error. Diagnostic trace might provide additional information. |
| MQJCA4019 | ActivationSpec ''JCA_ENDPOINT'' reconnected successfully. | An activationSpec has been successfully reconnected following a connection failure. | This is for information only. No action necessary. |
| MQJCA4020 | ActivationSpec ''JCA_ENDPOINT'' was unable to connect. Startup reconnection is being enabled. | An activationSpec was unable to connect, and startup reconnection is being enabled. | This is for information only. No action necessary. |
| MQJCA4021 | Trying to reconnect ActivationSpec ''JCA_ENDPOINT''. | The startup reconnection helper is attempting to reconnect an activationSpec. | This is for information only. No action necessary. |
| MQJCA4022 | Waiting for ''JCA_PROPERTY_VALUE'' milliseconds before reconnecting ''JCA_ENDPOINT''. | The startup reconnection helper is waiting for a period of time before attempting to reconnect an activationSpec. | This is for information only. No action necessary. |
| MQJCA4023 | Startup reconnection failed for ActivationSpec ''JCA_ENDPOINT''. Exception details: ''JCA_JMS_EXCEPTION''. | The resource adapter was not able to connect an endpoint within the number of attempts specified by the startupReconnectionRetryCount property. | Make sure that the WebSphere MQ queue manager is running, and that any other required components such as a listener are also running. Examine the application server logs to determine which MDBs have failed and restart the MDBs manually. |
| MQJCA4024 | Caused by: ''JCA_JMS_EXCEPTION''. | A call to WebSphere MQ classes for JMS caused an exception to be thrown. | See the linked exception for details of the failure. |
| MQJCA4025 | Startup reconnection failed for ActivationSpec ''JCA_ENDPOINT''. No exception information is available. | The resource adapter was not able to connect an endpoint within the number of attempts specified by the startupReconnectionRetryCount property. | Make sure that the WebSphere MQ queue manager is running, and that any other required components such as a listener are also running. |
| MQJCA4026 | Transaction backed out with reason: ''JCA_XA_EXCEPTION''. | A call to xa_end or xa_rollback returned a reason code XA_RBROLLBACK, indicating the transaction was backed out by the queue manager. | This is for information only. No action necessary. |
| MQJCA4027 | Transaction heuristically committed. | A call to xa_commit returned a reason code XA_HEURCOM, indicating the transaction was heuristically committed by the queue manager. | This is for information only. No action necessary. |
| MQJCA4028 | Non-ASF delivery failed to start with Exception: ''JCA_CSI_EXCEPTION''. | The resource adapter attempted to start the Non-ASF delivery thread, but an error occurred. | This is an internal error. A linked exception or diagnostic trace might provide additional information. |
| MQJCA5001 | WMQ messaging : ''JCA_VERSION''. | ||
| MQJMS0000 | Method ''XMSC_INSERT_NAME'' has been invoked at an illegal or inappropriate time or if the provider is not in an appropriate state for the requested operation. | ||
| MQJMS0002 | WebSphere MQ classes for JMS attempted to set invalid connection's client id. | ||
| MQJMS0003 | Destination not understood or no longer valid. | ||
| MQJMS0004 | WebSphere MQ classes for JMS has given JMS Provider a message selector with invalid syntax. | ||
| MQJMS0005 | Unexpected end of stream has been reached when a StreamMessage or BytesMessage is being read. | ||
| MQJMS0006 | WebSphere MQ classes for JMS attempts to use a data type not supported by a message or attempts to read data in the wrong type. | ||
| MQJMS0007 | WebSphere MQ classes for JMS attempts to read a write-only message. | ||
| MQJMS0008 | WebSphere MQ classes for JMS attempts to write a read-only message. | ||
| MQJMS0009 | WebSphere MQ classes for JMS is unable to allocate the resources required for a method. | ||
| MQJMS0010 | Operation invalid because a transaction is in progress. | ||
| MQJMS0011 | Call to Session.commit resulted in a rollback of the current transaction. | ||
| MQJMS0012 | URI is not of the correct format: queue://qmgrName/queueName [name-value pairs]. | ||
| MQJMS1000 | Failed to create JMS message. | ||
| MQJMS1001 | Unknown acknowledge mode ''{0}''. | ||
| MQJMS1004 | Connection closed. | ||
| MQJMS1005 | Unhandled state transition from ''{0}'' to ''{1}''. | ||
| MQJMS1006 | invalid value for ''XMSC_INSERT_NAME'': ''XMSC_INSERT_VALUE''. | ||
| MQJMS1007 | failed to create instance of exit class ''{0}''. | ||
| MQJMS1008 | unknown value of transportType: ''{0}''. | ||
| MQJMS1009 | no constructor with string argument. | ||
| MQJMS1010 | not implemented. | ||
| MQJMS1011 | security credentials cannot be specified when using MQ bindings. | ||
| MQJMS1012 | no message listener. | ||
| MQJMS1013 | operation invalid whilst session is using asynchronous delivery. | ||
| MQJMS1014 | operation invalid for identified producer. | ||
| MQJMS1015 | unknown value of target client: ''{0}''. | ||
| MQJMS1016 | an internal error has occurred. Please contact your system administrator. Detail: ''{0}''. | ||
| MQJMS1017 | non-local MQ queue not valid for receiving or browsing. | ||
| MQJMS1018 | no valid connection available. | ||
| MQJMS1019 | invalid operation for non-transacted session. | ||
| MQJMS1020 | invalid operation for transacted session. | ||
| MQJMS1021 | recover failed: unacknowledged messages might not get redelivered. | ||
| MQJMS1022 | failed to redirect message. | ||
| MQJMS1023 | rollback failed. | ||
| MQJMS1024 | session closed. | ||
| MQJMS1025 | failed to browse message. | ||
| MQJMS1026 | ExceptionListener threw exception: ''{0}''. | ||
| MQJMS1027 | failed to reconstitute destination from ''{0}''. | ||
| MQJMS1028 | element name is null. | ||
| MQJMS1029 | property name is null. | ||
| MQJMS1030 | buffer supplied by application is too small. | ||
| MQJMS1031 | an internal error has occurred. Please contact your system administrator. | ||
| MQJMS1032 | close() failed because of ''{0}''. | ||
| MQJMS1033 | start() failed because of ''{0}''. | ||
| MQJMS1034 | MessageListener threw: ''{0}''. | ||
| MQJMS1042 | invalid Delivery Mode. | ||
| MQJMS1044 | String is not a valid hexadecimal number - ''{0}''. | ||
| MQJMS1045 | Number outside of range for double precision S/390 Float ''{0}''. | ||
| MQJMS1046 | The character set ''{0}'' is not supported. | ||
| MQJMS1047 | The map message has an incorrect format. | ||
| MQJMS1048 | The stream message has an incorrect format. | ||
| MQJMS1049 | The WebSphere MQ classes for JMS attempted to convert a byte array to a String. | ||
| MQJMS1050 | The MQRFH2 header has an incorrect format. | ||
| MQJMS1051 | JMS Message class. | ||
| MQJMS1052 | Unrecognizable JMS Message class. | ||
| MQJMS1053 | Invalid UTF-16 surrogate detected ''{0}''. | ||
| MQJMS1054 | Invalid XML escape sequence detected ''{0}''. | ||
| MQJMS1055 | The property or element in the message has incompatible datatype ''{0}''. | ||
| MQJMS1056 | Unsupported property or element datatype ''{0}''. | ||
| MQJMS1057 | Message has no session associated with it. | ||
| MQJMS1058 | Invalid message property name: ''{0}''. | ||
| MQJMS1059 | Fatal error - UTF8 not supported. | ||
| MQJMS1060 | Unable to serialize object. | ||
| MQJMS1061 | Unable to deserialize object. | ||
| MQJMS1062 | Exception occurred reading message body: ''{0}''. | ||
| MQJMS1063 | Another ''{0}'' character(s) omitted. | ||
| MQJMS1064 | Integer encoding: ''{0}''=Floating point encoding ''{1}''. | ||
| MQJMS1065 | Exception occurred writing message body. | ||
| MQJMS1066 | Invalid message element name: ''{0}''. | ||
| MQJMS1067 | timeout invalid for MQ. | ||
| MQJMS1068 | failed to obtain XAResource. | ||
| MQJMS1069 | Not allowed with XASession. | ||
| MQJMS1072 | Could not inquire upon Queue Manager name. | ||
| MQJMS1073 | Specified MQ Queue is neither a QLOCAL nor a QALIAS. | ||
| MQJMS1074 | Unable to process null message. | ||
| MQJMS1075 | Error writing dead letter header. | ||
| MQJMS1076 | Error reading dead letter header. | ||
| MQJMS1077 | Connection/destination mismatch. | ||
| MQJMS1078 | Invalid Session object. | ||
| MQJMS1079 | Unable to write message to dead letter queue. | ||
| MQJMS1080 | No Backout-Requeue queue defined. | ||
| MQJMS1081 | Message requeue failed. | ||
| MQJMS1082 | Failure while discarding message. | ||
| MQJMS1085 | Error writing RFH. | ||
| MQJMS1086 | Error reading RFH. | ||
| MQJMS1087 | Unrecognizable or invalid RFH content. | ||
| MQJMS1088 | Mixed-domain consumers acting on the same input is forbidden. | ||
| MQJMS1089 | Exception occurred reading message body: ''{0}''. | ||
| MQJMS1091 | operation invalid for unidentified producer. | ||
| MQJMS1093 | A null parameter was passed to the constructor: ''{0}''. | ||
| MQJMS1094 | Invalid quantityHint. | ||
| MQJMS1096 | Invalid MessageReference. | ||
| MQJMS1098 | Invalid MessageReference version. | ||
| MQJMS1099 | Invalid MQQueueAgentThread version. | ||
| MQJMS1102 | Multicast connection cannot be established. | ||
| MQJMS1103 | Lost ''{0}'' messages in reliable multicast mode. | ||
| MQJMS1104 | Multicast connection disconnected due to timeout. | ||
| MQJMS1105 | Cannot connect with a specific local port for disthub multicast. | ||
| MQJMS1106 | Unable to load the native library required for PGM/IP. | ||
| MQJMS1107 | A problem with the connection has occurred. | ||
| MQJMS1110 | JMS1.1 Operation not supported by this type. | ||
| MQJMS1111 | JMS1.1 The required Queues/Publish Subscribe services are not set up. | ||
| MQJMS1112 | JMS1.1 Invalid operation for domain specific object. | ||
| MQJMS1113 | JMS1.1 Invalid operation for cross domain object. | ||
| MQJMS1115 | Failed to inquire the properties of the base queue ''XMSC_INSERT_DESTINATION_NAME'' of alias queue ''XMSC_INSERT_STRING'', defaulting to backout threshold of ''XMSC_INSERT_VALUE''. Completion code ''XMSC_INSERT_COMP_CODE'' Reason code ''XMSC_INSERT_REASON'' | When running in WebSphere MQ messaging provider migration mode, the WebSphere MQ classes for JMS opened an alias queue and encountered an issue when inquiring the BOQNAME (backout requeue queue name) and BOTHRESH (backout threshold) properties of the base queue that the alias queue resolves to. | Check the completion and reason codes to determine the cause. If the reason code relates to required authorities, check that the connected user has inquire authority on the base queue referenced by the alias queue. To stop inquires on the base queue, set the property com.ibm.mq.jms.useDefaultBOValues=true, either in the WebSphere MQ classes for JMS configuration file or as a Java System Property. This will cause the WebSphere MQ classes for JMS to use the default backout threshold shown in the message. If the default backout threshold is 0, poison message handling will be disabled. |
| MQJMS1116 | Message ''XMSC_INSERT_MESSAGE_ID'', detected on the queue ''XMSC_INSERT_DESTINATION_NAME'' on queue manager ''XMSC_INSERT_QUEUE_MANAGER_NAME'', cannot be processed due to an invalid MQRFH2 header, and has been moved to the dead letter queue ''XMSC_INSERT_STRING''. | When running in WebSphere MQ messaging provider migration mode, a ConnectionConsumer, Activation Specification or WebSphere Application Server Listener Port detected a message that contained an invalid MQRFH2 header. Because the Report field in the MQMD for this message contained the option MQRO_DEAD_LETTER_Q, the message was moved to the dead letter queue. | Look at the message on the dead letter queue to determine why the MQRFH2 header is invalid, and modify the application that generated the message to ensure that the MQRFH2 header is valid. |
| MQJMS1117 | Message ''XMSC_INSERT_MESSAGE_ID'', detected on the queue ''XMSC_INSERT_DESTINATION_NAME'' on queue manager ''XMSC_INSERT_QUEUE_MANAGER_NAME'', cannot be processed due to to an invalid MQRFH2 header, and has been discarded. | When running in WebSphere MQ messaging provider migration mode, a ConnectionConsumer, Activation Specification or WebSphere Application Server Listener Port detected a message that contained an invalid MQRFH2 header. Because the Report field in the MQMD for this message contained the option MQRO_DISCARD_MSG, the message was discarded. | Modify the application that is responsible for generating the message, so that it generates messages containing valid MQRFH2 headers. |
| MQJMS2000 | failed to close MQ queue. | ||
| MQJMS2001 | MQ Queue reference is null. | ||
| MQJMS2002 | failed to get message from MQ queue. | ||
| MQJMS2003 | failed to disconnect queue manager. | ||
| MQJMS2004 | MQQueueManager reference is null. | ||
| MQJMS2005 | failed to create MQQueueManager for ''{0}''. | ||
| MQJMS2006 | MQ problem: ''{0}''. | ||
| MQJMS2007 | failed to send message to MQ queue. | ||
| MQJMS2008 | failed to open MQ queue ''{0}''. | ||
| MQJMS2009 | MQQueueManager.commit() failed. | ||
| MQJMS2010 | unknown value for MQ queue definitionType: ''{0}''. | ||
| MQJMS2011 | failed to inquire MQ queue depth. | ||
| MQJMS2012 | XACLOSE failed. | ||
| MQJMS2013 | invalid security authentication supplied for MQQueueManager. | ||
| MQJMS2014 | Queue manager rejected XA client connection. | ||
| MQJMS3000 | failed to create a temporary queue from ''{0}''. | ||
| MQJMS3001 | temporary queue already closed or deleted. | ||
| MQJMS3002 | temporary queue in use. | ||
| MQJMS3003 | cannot delete a static queue. | ||
| MQJMS3004 | failed to delete temporary queue. | ||
| MQJMS3005 | Publish/Subscribe failed due to ''{0}''. | ||
| MQJMS3006 | Topic reference is null. | ||
| MQJMS3008 | Failed to build command ''{0}''. | ||
| MQJMS3009 | Failed to publish command to MQ queue. | ||
| MQJMS3010 | Failed to build publish message. | ||
| MQJMS3011 | Failed to publish message to MQ queue. | ||
| MQJMS3013 | Failed to store admin entry. | ||
| MQJMS3014 | Failed to open subscriber queue ''{0}''. | ||
| MQJMS3017 | Failed to delete subscriber queue ''{0}''. | ||
| MQJMS3018 | Unknown durable subscription ''{0}''. | ||
| MQJMS3019 | TemporaryTopic already deleted. | ||
| MQJMS3020 | TemporaryTopic out of scope. | ||
| MQJMS3021 | Invalid subscriber queue prefix: ''{0}''. | ||
| MQJMS3022 | Durable re-subscribe must use same subscriber queue; specified:''{0}'' original:''{1}''. | ||
| MQJMS3023 | Subscription has an active TopicSubscriber. | ||
| MQJMS3024 | Illegal use of uninitialized client ID. | ||
| MQJMS3025 | TemporaryTopic in use. | ||
| MQJMS3026 | QueueSender is closed. | ||
| MQJMS3028 | TopicPublisher is closed. | ||
| MQJMS3031 | Can't set clientID after connection has been used. | ||
| MQJMS3032 | Resetting the clientID is not allowed. | ||
| MQJMS3033 | QueueReceiver is closed. | ||
| MQJMS3034 | TopicSubscriber is closed. | ||
| MQJMS3037 | Message Producer is closed. | ||
| MQJMS3038 | Message Consumer is closed. | ||
| MQJMS3039 | Illegal use of null name. | ||
| MQJMS3040 | Invalid broker control message content: ''{0}''. | ||
| MQJMS3041 | Field ''{0}'' already set. | ||
| MQJMS3042 | Unrecognizable message from Pub/Sub Broker. | ||
| MQJMS3043 | Invalid Level for repeating Cleanup. | ||
| MQJMS3044 | Cleanup level of NONE requested. | ||
| MQJMS3045 | Failed to open ''{0}'': maybe a FORCE or NONDUR level cleanup is running? | ||
| MQJMS3046 | Failed to open ''{0}'': maybe another JMS application is using Pub/Sub with this queue manager? | ||
| MQJMS3047 | Subscription Store type not supported by queue manager. | ||
| MQJMS3048 | Incorrect Subscription Store type. | ||
| MQJMS3049 | MQJMS_Messages.MQJMS_PS_WRONG_SUBSCRIPTION_TYPE = Incorrect Subscription type for this Subscription Store. | ||
| MQJMS3050 | Subscription is already in use and cannot be updated. | ||
| MQJMS3051 | Invalid Subscription name. | ||
| MQJMS3052 | Cleanup started at ''XMSC_INSERT_TIMESTAMP'' on ''XMSC_INSERT_DATESTAMP''. | The WebSphere MQ classes for JMS Cleanup script is running and has started a cleanup operation at the time and date specified. The time is in the format HHMMSSTH, and the date is in the format YYYYMMDD. | None. |
| MQJMS3053 | Cleanup finished at ''XMSC_INSERT_TIMESTAMP'' on ''XMSC_INSERT_DATESTAMP''. | The WebSphere MQ classes for JMS Cleanup script is running and has finished a cleanup operation at the time and date specified. The time is in the format HHMMSSTH, and the date is in the format YYYYMMDD. | None. |
| MQJMS3054 | Time until next Cleanup operation : ''XMSC_INSERT_STRING'' minutes. | The WebSphere MQ classes for JMS Cleanup script is running and is now waiting for the number of minutes shown in the message before starting the next cleanup operation. The number of minutes shown in the message is rounded down to the nearest minute. | None. |
| MQJMS4124 | Property value for ''{0}'' is null. | ||
| MQJMS4125 | Invalid property for a ''{0}'': ''{1}''. | ||
| MQJMS4131 | Expected and actual object types do not match. | ||
| MQJMS5053 | *** No broker response. Please ensure that the broker is running. If you are using the WebSphere MQ broker check that your brokerVersion is set to V1 *** | ||
| MQJMS5087 | Unexpected error ''{1}'' accessing internal queue ''{0}''. | ||
| MQJMS6040 | Invalid socket family name: ''{0}''. | ||
| MQJMS6041 | An exception occurred while attempting to load socket factory class ''{0}'', exception: <''{1}''>. | ||
| MQJMS6056 | Cannot change parameter ''{0}'' since no more BaseConfig parameter changes are allowed. | ||
| MQJMS6057 | Cannot set parameter ''{0}'' to value ''{1}''. | ||
| MQJMS6058 | error occurred while getting BaseConfig parameter ''{0}''. | ||
| MQJMS6059 | An exception occurred while loading the minimal client security implementation. | ||
| MQJMS6060 | An unexpected exception in minimal client, ''{0}''. | ||
| MQJMS6061 | A specified topic was malformed, ''{0}''. | ||
| MQJMS6062 | EOF was encountered while receiving data in the minimal client. | ||
| MQJMS6063 | The broker indicated an error on the minimal client connection. | ||
| MQJMS6064 | Connector.send was called with an illegal message value. | ||
| MQJMS6065 | An illegal value was encountered for a field, ''{0}''. | ||
| MQJMS6066 | An unexpected internal error occurred in the minimal client. | ||
| MQJMS6067 | A bytes message operation was requested on something that is not a bytes message. | ||
| MQJMS6068 | A text message operation was requested on something that is not a text message. | ||
| MQJMS6069 | A stream message operation was requested on something that is not a stream message. | ||
| MQJMS6070 | A map message operation was requested on something that is not a map message. | ||
| MQJMS6071 | The broker sent an invalid message during authentication. | ||
| MQJMS6072 | The broker requested an unavailable protocol during authentication. | ||
| MQJMS6073 | Minimal client connection rejected because of authentication failure. | ||
| MQJMS6074 | No QOP available in the minimal client. | ||
| MQJMS6079 | An exception occurred while attempting to load thread pooling support, ''{0}''. | ||
| MQJMS6081 | An attempt was made to read from a Stream message before a previous read has completed. | ||
| MQJMS6083 | An exception occurred while initializing a thread pool instance, ''{0}''. | ||
| MQJMS6085 | No ExceptionListener has been set. | ||
| MQJMS6088 | The client-side connection monitor is terminating. | ||
| MQJMS6090 | Attempted to synchronously receive on a MessageConsumer for which a listener is active. | ||
| MQJMS6091 | An IOException occured when starting or stopping delivery on the connection, ''{0}''. | ||
| MQJMS6093 | An exception occured during synchronous receive, ''{0}''. | ||
| MQJMS6096 | A JMSPriority level of ''{0}'' is outside the range specified in JMS. | ||
| MQJMS6097 | The specified JMSMessageID, ''{0}'', is invalid. | ||
| MQJMS6105 | No more client parameter changes allowed. | ||
| MQJMS6106 | An exception occured when initializing parameter ''{0}'', exception ''{1}''. | ||
| MQJMS6115 | An exception occured while creating the TopicConnection, ''{0}''. | ||
| MQJMS6116 | This operation is not permitted on an entity that is closed. | ||
| MQJMS6117 | The ''{0}'' implementation of Topic is not supported. | ||
| MQJMS6118 | Topic ''{0}'' contains a wildcard which is invalid for publishing. | ||
| MQJMS6119 | An IOException occured while publishing, ''{0}''. | ||
| MQJMS6120 | Attempted to use a temporary topic not created on the current connection. | ||
| MQJMS6121 | An IOException occured while subscribing, ''{0}''. | ||
| MQJMS6228 | Minimal client authentication failed because exception ''{0}''. | ||
| MQJMS6229 | QOP required but disabled for this minimal client. | ||
| MQJMS6232 | While creating a TopicSubscriber, attempting to add the subscription to the matching engine resulted in the following exception: ''{0}''. | ||
| MQJMS6233 | An unexpected exception was caught in the matching engine: ''{0}''. | ||
| MQJMS6234 | An attempt was made to remove an object with topic ''{0}'' from an empty matching engine: ''{1}''. | ||
| MQJMS6235 | An attempt was made to remove an object with topic ''{0}'' from the matching engine, but it did not have a cache entry: ''{1}''. | ||
| MQJMS6236 | An unknown check type of class ''{0}'' was encountered in a type-specific matcher. | ||
| MQJMS6237 | An attempt was made to access an unknown field named ''{0}''. | ||
| MQJMS6238 | In attempting to access a field of a message=the following exception occurred: ''{0}''. | ||
| MQJMS6239 | An EvalCache get or put operation occurred when the cache was not loaded. | ||
| MQJMS6240 | An EvalCache get or put operation specified an invalid id. | ||
| MQJMS6241 | Too many content attributes were specified. | ||
| MQJMS6242 | A duplicate MatchTarget was detected in MatchSpace. | ||
| MQJMS6243 | An attempt was made to remove MatchTarget ''{0}'' from MatchSpace, but it has no key (topic). | ||
| MQJMS6244 | The MatchTarget ''{1}'' with key (topic) ''{0}'' could not be removed from MatchSpace because it could not be found. | ||
| MQJMS6245 | An attempt was made to add a MatchTarget to MatchSpace without a key (topic). | ||
| MQJMS6246 | An incorrect use of a the topic wildcard character ''{0}'' was detected. | ||
| MQJMS6247 | The topic segment separator ''{0}'' appears in an incorrect position. | ||
| MQJMS6248 | An error occurred while trying to load or invoke the subscription selector parser. | ||
| MQJMS6249 | The following exception occurred while parsing a subscription selector: ''{0}''. | ||
| MQJMS6250 | The escape character was used to terminate the following pattern: ''{0}''. | ||
| MQJMS6251 | The escape character ''{0}'' passed to the pattern tool is longer than one character. | ||
| MQJMS6252 | A message field was expected to contain a value of type ''{0}'' but contained one of type ''{1}''. | ||
| MQJMS6311 | Transport type 'DIRECT' within a transaction is not supported. | ||
| MQJMS6312 | Non-authorized subscription to topic ''{0}''. | ||
| MQJMS6350 | An object message operation was requested on something that is not an object message. | ||
| MQJMS6351 | An exception occurred when creating subscription to <''{0}'',''{1}''>, ''{2}''. | ||
| MQJMS6401 | Persistent messages not supported for transport type 'DIRECT'. | ||
| MQJMS6402 | Time to Live > 0 not supported for transport type 'DIRECT'. | ||
| MQJMS6403 | Topic Expiry > 0 not supported for transport type 'DIRECT'. | ||
| MQJMS6404 | Client Acknowledge not supported for transport type 'DIRECT'. |
(C) Copyright IBM Corporation 2018. All rights reserved.