Express (Distributed operating systems), v8.0 > Reference > Messages
CWWMQ
CWWMQ0001E: An internal error occurred. The endpoint name is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0002E: An internal error occurred. The message endpoint factory is of type {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0003E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0004E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0005E: An internal error occurred. The message endpoint factory is of type {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0006E: An internal error occurred. The message endpoint factory is of type {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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}.
Explanation The system has detected a problem with the MDB associated with the message endpoint and has paused the delivery of messages to the message endpoint. Action Investigate possible problems with the MDB that could cause sequential failures. When you are ready to resume delivery of messages to the endpoint, use the administrative console or message endpoint MBean to restart the endpoint named in the message.
CWWMQ0008E: An internal error occurred. The message endpoint {0} could not be paused, despite the endpoint repeatedly failing to deliver messages.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0009E: An internal error occurred. Runtime environment is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0010E: An internal error occurred. Runtime environment is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0011E: An internal error occurred {0}, which prevented the initialization of the routines responsible for classification of WebSphere MQ messaging workloads.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0012E: An internal error occurred. The error message is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0013E: An internal error occurred. The selector, {0}, was not present in the selector cache.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0014E: An internal error has occurred. The error message is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0015E: An internal error occurred. The wildcard topic expression, {0}, was not present in the discriminator cache.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0016W: The z/OS workload classification document contains more than one WMQRAClassification element that specifies a default transaction class.
Explanation The z/OS workload classification document contains more than one WMQRAClassification element that specifies a default transaction class. Only the first default transaction class attribute is used. Action Update the z/OS workload classification document so that it contains only one WMQRAClassification element.
CWWMQ0017W: A classification rule, specified by the wmqra_classification_info element in the classification document, contains an incorrectly specified selector of ''{0}''.
Explanation An incorrectly specified selector was encountered in the classification document. The rule which specifies the selector will be ignored. Action Review your classification document to identify the incorrectly specified selector. Correct the selector then restart the affected application server processes.
CWWMQ0018W: A classification rule, specified by the wmqra_classification_info element in the classification document, contains an incorrectly specified topic name of ''{0}''.
Explanation An incorrectly specified topic name was encountered in the classification document. The rule that specifies the topic will be ignored. Action Review your classification document to identify the incorrectly specified topic name. Correct the topic name then restart the affected application server processes.
CWWMQ0019W: An internal error occurred. The error message is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0020I: The system default workload management transaction class of {0} is being used to classify WebSphere MQ messaging provider workloads.
Explanation No default workload classification for WebSphere MQ messaging provider workloads is present in the workload classification rules document. The specified system default classification is assigned to inbound messages that do not meet any other classification criteria. Action This message is for informational purposes only. No action is required. To use a transaction class other than the system default transaction class, update your classification document then restart the affected server or servers.
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.
Explanation WebSphere MQ messaging provider workload classification rules that specify queue URIs must include a queue manager component in the URI or the rule will be ignored. Action Correct the classification rule to include an appropriate queue component then restart the affected servers. Information about the expected format for queue URIs can be found in the WebSphere MQ product documentation.
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.
Explanation The specified queue name does not conform to the rules for valid WebSphere MQ queue names. The WebSphere MQ messaging provider classification rule that specifies the queue name will be ignored. Action Correct the queue name then restart the affected servers. Information about the naming rules for WebSphere MQ queues can be found in the WebSphere MQ product documentation.
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.
Explanation The specified queue URI does not conform to the rules for valid WebSphere MQ queue URIs. The rule that specified the URI is being ignored and will not be used to classify WebSphere MQ messaging provider workloads. Action Correct the queue URI then restart the affected servers. Information about the format for queue URIs can be found in the WebSphere MQ product documentation.
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.
Explanation The specified queue manager name does not conform to the rules for naming WebSphere MQ queue managers. The rule that specifies this queue manager name will be ignored and not used to classify WebSphere MQ messaging provider messaging workloads. Action Correct the queue manager name so that it conforms to the rules for naming WebSphere MQ queue managers. Information about the WebSphere MQ queue manager naming rules can be found in the WebSphere MQ product documentation.
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.
Explanation The specified topic URI does not conform to the rules for valid WebSphere MQ topic URIs. The rule that specified the URI is being ignored and will not be used to classify WebSphere MQ messaging provider workloads. Action Correct the topic URI then restart the affected servers. Information about the format for topic URIs can be found in the WebSphere MQ product documentation.
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.
Explanation The specified destination URI does not conform to the rules for valid WebSphere MQ destination URIs. The rule that specified the destination URI is being ignored and will not be used to classify WebSphere MQ messaging provider workloads. Action Correct the destination URI then restart the affected servers. Information about the format of destination URIs can be found in the WebSphere MQ product documentation.
CWWMQ0031E: An internal error has occurred. An unexpected resource type has been encountered: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0032E: An internal error has occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0033E: An internal error has occurred. The exception was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0034E: An internal error has occurred. The error was {0}. The associated class is {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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}.
Explanation When configuring a WebSphere MQ messaging provider connection factory an attempt to set a property on it failed with the provided error. Configuration of the connection factory will continue. Action Check that the configuration for the WebSphere MQ messaging provider connection factory is correct.
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}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0043E: An internal error has occurred. The connection factory class name was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0044E: An internal error has occurred. An error, with message {0}, caused endpoint {1} to be stopped.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0045E: An internal error has occurred. An error, with message {0}, caused endpoint {1} to be stopped.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0046E: An internal error has occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0047E: No queue manager name could be determined for endpoint {0}.
Explanation A queue manager name could not be determined for the specified endpoint. Any classifications rules that specify queue manager name based matches are not applied to messages received from this endpoint. Action Either ensure that the corresponding activation specification has a queue manager name specified, or ensure that the identity used to connect to WebSphere MQ has sufficient privileges to inquire on the name of the queue manager.
CWWMQ0049E: An internal error has occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0050E: An internal error has occurred. The expected length of serialized data was {0}, but the actual length was {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0051E: An internal error has occurred. The exception was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0052E: An internal error has occurred. The error was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0053E: An internal error has occurred. The error was {0}. The object is {1} which is of type {2}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0054E: An internal error has occurred. The error was {0}. The object is {1}, which is of type {2}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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}.
Explanation The specified WebSphere MQ messaging provider connection factory cannot connect to WebSphere MQ using SSL because the host name of the target queue manager is incorrect. Action Correct the host name. See the accompanying error messages for further information.
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}.
Explanation The specified WebSphere MQ messaging provider connection factory cannot connect to WebSphere MQ using SSL because the port number of the target queue manager is incorrect. Action Correct the port number. See the accompanying error messages for further information.
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.
Explanation To locate a SSLSocketFactory by direct lookup, the sslAliasName is required. This attribute is missing. Action Use the administrative console to provide a value for the sslAliasName.
CWWMQ0058E: An unexpected value for the WMQRA_SSL_SETTING property has been received. The value received was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0059E: An internal error has occurred. The exception was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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.
Explanation The use of a WebSphere MQ messaging provider connection factory with a connection type of bindings does not require SSL information to be configured. Action If the SSL information is for use at a later date, ignore this message. Otherwise, delete the unnecessary information.
CWWMQ0061E: An internal error occurred. The expected class name was {0}. The actual class name was {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0062E: An SSL alias was provided with name {0}. However no SSL alias with this name exists.
Explanation To locate a SSLSocketFactory by direct lookup, an SSL alias name is required. However no SSL alias with the supplied name exists. Action Create an SSL alias with the desired name or update the configuration to use the correct SSL alias name. Then retry the operation.
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}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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}.
Explanation An SSLSocketFactory was not created. Action See the accompanying error messages for further information.
CWWMQ0065E: An internal error occurred. An unexpected segment type was received. The value was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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}.
Explanation The nativepath field from the WebSphere MQ resource adapter configuration is used to establish the name of the directory which contains the WebSphere MQ native libraries. However, the nativepath field is either blank, incorrectly formatted or doesn't reference a directory. An attempt will be made to use the MQ_INSTALL_ROOT variable to establish this information instead. Action If the MQ_INSTALL_ROOT variable is correctly set, no action is required. Otherwise, set the nativepath field on the WebSphere MQ resource adapter configuration to reference the directory containing the WebSphere MQ native libraries.
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}.
Explanation An attempt has been made to locate the directory that contains the WebSphere MQ native libraries by expanding the MQ_INSTALL_ROOT variable. However the value resulting from this expansion represents a path that does not exist or is not a directory. Action Verify that the MQ_INSTALL_ROOT variable is correctly set to reference the location of a WebSphere MQ installation.
CWWMQ0068E: The installation root of the WebSphere MQ resource adapter cannot be established. The error message was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0069E: The installation directory for the WebSphere MQ resource adapter does not exist. The expected directory path is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0070E: The META-INF directory for the WebSphere MQ resource adapter does not exist. The expected directory path is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0071E: The ra.xml file for the WebSphere MQ resource adapter does not exist. The expected path for the file is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0072E: The manifest file for the WebSphere MQ resource adapter does not exist. The expected path for the file is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0073E: The manifest file for the WebSphere MQ resource adapter cannot be opened. The error message was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0074E: It was not possible to load properties from the WebSphere MQ resource adapter manifest file. The exception message was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0075E: The Implementation-Title property was missing from the WebSphere MQ resource adapter manifest file.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0076E: The value of the Implementation-Title property from the WebSphere MQ resource adapter manifest file was unexpected. The value was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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}.
Explanation When configuring the WebSphere MQ resource adapter it is possible to set its nativepath attribute. This attribute has been set with multiple directory names when only one is expected. Action Specify a single directory name for the nativepath attribute of the WebSphere MQ resource adapter.
CWWMQ0083E: An internal error occurred. A WebSphere MQ messaging provider connection factory could not be created.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0084E: WMQConnectivityTester MBean could not be activated. The error was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0086E: An internal error has occurred. The error was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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}.
Explanation A WebSphere MQ messaging provider connection factory only uses a single cipher suite when connecting to a queue manager via SSL. If the SSL settings specify multiple cipher suites then only the first one will be used. Action Configure your SSL settings so that only a single cipher suite is available.
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}.
Explanation The specified WebSphere MQ messaging provider connection factory already has a cipher suite set and it is not the same as the one chosen from the SSL configuration. The cipher suite from the connection factory will be used instead of the value from the SSL settings. Action Consider whether the value of the cipher suite on the connection factory should match the value specified in the SSL settings and modify the configuration appropriately.
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}.
Explanation A problem has been detected while testing a topic name against a topic wildcard expression. The most likely reason for this is a badly formatted topic name. Action Check that the specified topic name is correctly formatted.
CWWMQ0090E: An unexpected class name was received. The class name was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMQ0091E: An internal error occurred. Unexpected object type {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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}.
Explanation A cipher suite needs to be specified in the SSL settings that are used to secure communications between a WebSphere MQ messaging provider connection factory and a WebSphere MQ queue manager. However there is no cipher suite specified. Action Configure your SSL settings so that only a single cipher suite is available.
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.
Explanation The use of WebSphere MQ messaging provider activation specifications on the z/OS platform requires that the control region adjunct process be started. However, the control region adjunct process has not been configured to start. Action Modify the application server configuration so that the control region adjunct process can be started.
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.
Explanation A possible discrepancy between the JVM and the native libraries used by the WebSphere MQ resource adapter has been detected. This may cause undesirable behaviour. Action Check that the path specified either by the WebSphere MQ resource adapter nativepath attribute or the MQ_INSTALL_ROOT variable is a directory which contains native libraries that are compatible with the JVM used by the application server.
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.
Explanation A possible discrepancy between the JVM and the native libraries used by the WebSphere MQ resource adapter has been detected. This may cause undesirable behaviour. Action Check that the path specified either by the WebSphere MQ resource adapter nativepath attribute or the MQ_INSTALL_ROOT variable is a directory which contains native libraries that are compatible with the JVM used by the application server.
CWWMQ9999E: {0}
Explanation If the message does not give sufficient information, check previous messages for further help. Action If you are not able to resolve the problem ask the system administrator to help resolve the problem.