CWWMQ

CWWMQ0001E: An internal error occurred. The endpoint name is {0}.
CWWMQ0002E: An internal error occurred. The message endpoint factory is of type {0}.
CWWMQ0003E: An internal error occurred.
CWWMQ0004E: An internal error occurred.
CWWMQ0005E: An internal error occurred. The message endpoint factory is of type {0}.
CWWMQ0006E: An internal error occurred. The message endpoint factory is of type {0}.
CWWMQ0007W: The message endpoint {0} has been paused by the system. Message delivery failed to the endpoint more than {1} times. The last attempted delivery failed with the following error: {2}.
CWWMQ0008E: An internal error occurred. The message endpoint {0} could not be paused, despite the endpoint repeatedly failing to deliver messages.
CWWMQ0009E: An internal error occurred. Runtime environment is {0}.
CWWMQ0010E: An internal error occurred. Runtime environment is {0}.
CWWMQ0011E: An internal error occurred {0}, which prevented the initialization of the routines responsible for classification of WebSphere MQ messaging workloads.
CWWMQ0012E: An internal error occurred. The error message is {0}.
CWWMQ0013E: An internal error occurred. The selector, {0}, was not present in the selector cache.
CWWMQ0014E: An internal error has occurred. The error message is {0}.
CWWMQ0015E: An internal error occurred. The wildcard topic expression, {0}, was not present in the discriminator cache.
CWWMQ0016W: The z/OS workload classification document contains more than one WMQRAClassification element that specifies a default transaction class.
CWWMQ0017W: A classification rule, specified by the wmqra_classification_info element in the classification document, contains an incorrectly specified selector of ''{0}''.
CWWMQ0018W: A classification rule, specified by the wmqra_classification_info element in the classification document, contains an incorrectly specified topic name of ''{0}''.
CWWMQ0019W: An internal error occurred. The error message is {0}.
CWWMQ0020I: The system default workload management transaction class of {0} is being used to classify WebSphere MQ messaging provider workloads.
CWWMQ0021W: A wmqra_classification_info element of the workload classification document specifies a queue URI of ''{0}'', which has no queue manager component. The classification rule is being ignored.
CWWMQ0022W: A wmqra_classification_info element of the workload classification document specifies a queue name of ''{0}'', which is not a valid WebSphere MQ queue name. The classification rule is being ignored.
CWWMQ0023W: A wmqra_classification_info element of the workload classification document specifies a queue URI of ''{0}'', which is not a valid WebSphere MQ queue URI. The classification rule is being ignored.
CWWMQ0026W: A wmqra_classification_info element of the workload classification document specifies a queue manager name of ''{0}'' using a queue_manager attribute. The value does not conform to the rules for naming WebSphere MQ queue managers and therefore the rule will be ignored.
CWWMQ0028W: A wmqra_classification_info element of the workload classification document specifies a topic URI of ''{0}'', which does not conform to the rules for valid WebSphere MQ topic URIs. The classification rule is being ignored.
CWWMQ0030W: A wmqra_classification_info element of the workload classification document specifies a destination URI of ''{0}'', which does not conform to the rules for valid WebSphere MQ destination URIs manager names. The classification rule is being ignored.
CWWMQ0031E: An internal error has occurred. An unexpected resource type has been encountered: {0}.
CWWMQ0032E: An internal error has occurred.
CWWMQ0033E: An internal error has occurred. The exception was {0}.
CWWMQ0034E: An internal error has occurred. The error was {0}. The associated class is {1}.
CWWMQ0035E: An attempt to set a property on a WebSphere MQ messaging provider connection factory failed with an error. The error message was ''{0}''. The property name was {1}, with value {2} of type {3}. The Connection Factory was of type {4}.
CWWMQ0036E: An internal error has occurred. The error message was ''{0}''. The property name was {1}, with value {2} of type {3}. The connection factory was {4}.
CWWMQ0043E: An internal error has occurred. The connection factory class name was {0}.
CWWMQ0044E: An internal error has occurred. An error, with message {0}, caused endpoint {1} to be stopped.
CWWMQ0045E: An internal error has occurred. An error, with message {0}, caused endpoint {1} to be stopped.
CWWMQ0046E: An internal error has occurred.
CWWMQ0047E: No queue manager name could be determined for endpoint {0}.
CWWMQ0049E: An internal error has occurred.
CWWMQ0050E: An internal error has occurred. The expected length of serialized data was {0}, but the actual length was {1}.
CWWMQ0051E: An internal error has occurred. The exception was {0}.
CWWMQ0052E: An internal error has occurred. The error was {0}.
CWWMQ0053E: An internal error has occurred. The error was {0}. The object is {1} which is of type {2}.
CWWMQ0054E: An internal error has occurred. The error was {0}. The object is {1}, which is of type {2}.
CWWMQ0055E: The host name of the target queue manager for the WebSphere MQ messaging provider connection factory {0} is incorrect. The incorrect host name is {1}.
CWWMQ0056E: The port number of the target queue manager for the WebSphere MQ messaging provider connection factory {0} is incorrect. The incorrect port number is {1}.
CWWMQ0057E: An attempt to locate a SSLSocketFactory for the WebSphere MQ messaging provider connection factory {0} has been made using a direct lookup but the sslAliasName property is null or empty.
CWWMQ0058E: An unexpected value for the WMQRA_SSL_SETTING property has been received. The value received was {0}.
CWWMQ0059E: An internal error has occurred. The exception was {0}.
CWWMQ0060W: The SSL information that has been configured for the WebSphere MQ messaging provider connection factory {0} is not required because the configured transportType is bindings.
CWWMQ0061E: An internal error occurred. The expected class name was {0}. The actual class name was {1}.
CWWMQ0062E: An SSL alias was provided with name {0}. However no SSL alias with this name exists.
CWWMQ0063E: The call to JSSEHelper.getSSLSocketFactory() failed with an error. The error message was {0}. The values passed to JSSEHelper.getSSLSocketFactory() were {1}, {2} and {3}.
CWWMQ0064E: It was not possible to create an SSLSocketFactory. The provided port number was {0}. The provided host name was {1}. The provided SSL alias was {2}.
CWWMQ0065E: An internal error occurred. An unexpected segment type was received. The value was {0}.
CWWMQ0066W: The name of the directory which contains the WebSphere MQ native libraries cannot be established using the nativepath field from the WebSphere MQ resource adapter configuration. The MQ_INSTALL_ROOT variable will be used to establish this information instead. The nativepath field was {0}.
CWWMQ0067W: The name of the directory which contains the WebSphere MQ native libraries cannot be established by expanding the MQ_INSTALL_ROOT variable. The calculated value for the directory was {0}.
CWWMQ0068E: The installation root of the WebSphere MQ resource adapter cannot be established. The error message was {0}.
CWWMQ0069E: The installation directory for the WebSphere MQ resource adapter does not exist. The expected directory path is {0}.
CWWMQ0070E: The META-INF directory for the WebSphere MQ resource adapter does not exist. The expected directory path is {0}.
CWWMQ0071E: The ra.xml file for the WebSphere MQ resource adapter does not exist. The expected path for the file is {0}.
CWWMQ0072E: The manifest file for the WebSphere MQ resource adapter does not exist. The expected path for the file is {0}.
CWWMQ0073E: The manifest file for the WebSphere MQ resource adapter cannot be opened. The error message was {0}.
CWWMQ0074E: It was not possible to load properties from the WebSphere MQ resource adapter manifest file. The exception message was {0}.
CWWMQ0075E: The Implementation-Title property was missing from the WebSphere MQ resource adapter manifest file.
CWWMQ0076E: The value of the Implementation-Title property from the WebSphere MQ resource adapter manifest file was unexpected. The value was {0}.
CWWMQ0082W: The WebSphere MQ resource adapter has been configured with a nativepath attribute that contains more than one directory name. The number of directory names is {0}.
CWWMQ0083E: An internal error occurred. A WebSphere MQ messaging provider connection factory could not be created.
CWWMQ0084E: WMQConnectivityTester MBean could not be activated. The error was {0}.
CWWMQ0085E: The ''suspend message delivery to failing endpoints'' configuration parameter has been specified but the configured ''number of sequential delivery failures before suspending endpoint'' parameter is incorrect or missing. The value of the ''number of sequential delivery failures before suspending endpoint'' parameter is {0}.
CWWMQ0086E: An internal error has occurred. The error was {0}.
CWWMQ0087W: The SSL settings that will be used by a WebSphere MQ messaging provider connection factory to connect to WebSphere MQ specify multiple cipher suites. Only the first cipher suite in the list will be used. The available cipher suites are {0}. The description of the connection factory is {1}.
CWWMQ0088W: The SSL settings that will be used by a WebSphere MQ messaging provider connection factory to connect to WebSphere MQ specify the following cipher suite {0}. However, the connection factory already has a cipher suite set and it is different. The value of the cipher suite from the connection factory is {1}. The cipher suite from the connection factory will be used instead of the value from the SSL settings. The description of the connection factory is {2}.
CWWMQ0089E: A problem has been detected while testing a topic name against a topic wildcard expression. The topic wildcard expression is {0}. The topic name is {1}. The error message is {2}.
CWWMQ0090E: An unexpected class name was received. The class name was {0}.
CWWMQ0091E: An internal error occurred. Unexpected object type {0}.
CWWMQ0092W: The SSL settings that will be used by a WebSphere MQ messaging provider connection factory to connect to WebSphere MQ do not contain any cipher suites. The description of the connection factory is {0}.
CWWMQ0093W: An attempt has been made to use a WebSphere MQ messaging provider activation specification. However the control region adjunct process has not been configured to start, so the activation specification will not function correctly.
CWWMQ0094W: A 64 bit JVM has been detected, however the path to the directory ''{0}'' which is expected to contain the WebSphere MQ native libraries appears to contain 32 bit libraries.
CWWMQ0095W: A 32 bit JVM has been detected, however the path to the directory ''{0}'' which is expected to contain the WebSphere MQ native libraries appears to contain 64 bit libraries.
CWWMQ9999E: {0}


Terms and conditions for information centers | Feedback

Last updated: June 12, 2013 12:15 PM EDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.wmqra.CWWMQMessages.dita
File name: com.ibm.ws.wmqra.CWWMQMessages.html