Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | To locate a SSLSocketFactory by direct lookup, a 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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An SSLSocketFactory was not created. |
Action | See the accompanying error messages for further information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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 your configuration appropriately. |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
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. |
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. |
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 your system administrator to help resolve the problem. |