Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The connection to the remote messaging engine failed. This is possibly because the messaging engine is not started, or the port or host name specified was incorrect. |
Action | Ensure the messaging engine is running, the connection properties are correct and repeat the operation. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A method was invoked on a consumer, browser or producer session that had already been closed. |
Action | Ensure that the method call is performed before the session is closed. |
Explanation | A method was invoked on a connection object that had already been closed. |
Action | Ensure that the method call is performed before the connection is closed. |
Explanation | An attempt was made to register or deregister an asynchronous consumer callback for a consumer session that is started. |
Action | Ensure the consumer session is in a stopped state before attempting to register or deregister an asynchronous consumer callback. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to unlock an incorrect message in a locked message enumeration. |
Action | Ensure that, before invoking the unlock method, the locked message enumeration cursor resides on a message for which the unlock operation is valid. |
Explanation | An attempt was made to delete an incorrect message in a locked message enumeration. |
Action | Ensure that, before invoking the delete method, the locked message enumeration cursor resides on a message for which the delete operation is valid. |
Explanation | The maximum number of open sessions for a connection has been reached, and an attempt was made to open a further session. |
Action | Close any sessions that are not required and repeat the operation. |
Explanation | A synchronous consumer session method has been invoked while a asynchronous consumer callback is registered for the session. |
Action | Unregister the asynchronous consumer callback before invoking synchronous methods on a consumer session. |
Explanation | The invoked method is valid only on an in-process client and is not allowed to be called from a remote client. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A transaction becomes complete once commit or rollback has been called for the transaction. |
Action | Ensure commit or rollback are not called more than once on the same transaction object. |
Explanation | Connection to a remote messaging engine was successful, but the client and server cannot agree on appropriate connection values. |
Action | Ensure that the client is using valid connection values for the server you are connecting to and try again. |
Explanation | When attempting to log in, the server rejected the user information supplied. |
Action | Ensure the user information is correct and try again. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This application server is now accepting messaging connection requests from clients and other messaging engines. |
Action | No action required. |
Explanation | The server failed to run an unlockSet() command on behalf of the remote client. |
Action | Ask your system administrator to examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The server transport failed to initialize. The messaging engine may not be able to accept remote connections. |
Action | Ask your system administrator to examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to run an unlockSet() command on behalf of the remote client. |
Action | Ask your system administrator to examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | The server failed to run a deleteSet() or deleteAll() command on behalf of the remote client. |
Action | Ask your system administrator to examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | An operation performed within the transaction boundary failed. As such, this transaction has been rolled back to ensure integrity of data. The failure was logged in the system logs and an FFDC record was generated to help you diagnose the cause of the failure. |
Action | Ask your system administrator to examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | It was not possible to send a transacted or non-reliable message due to the stated exception. |
Action | Ask your system administrator to examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to run a deleteSet() or deleteAll() command on behalf of the remote client. |
Action | Ask your system administrator to examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | An operation performed within the transaction boundary failed. As such, this transaction has been rolled back to ensure integrity of data. The failure was logged in the system logs and an FFDC record was generated to help you diagnose the cause of the failure. |
Action | Ask your system administrator to examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | The remote messaging engine has performed a controlled close of the connection. It may be shutting down, or there may be a problem with the network. |
Action | If the remote messaging engine was not shutting down verify the network is working correctly. You may need to ask your system administrator to examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | Multicast consumption only was requested by a client but this messaging engine does not support it. |
Action | Either enable the server to allow multicast message consumption or allow the client to use unicast message consumption. |
Explanation | The server failed to run an unlockSet() command on behalf of the remote client. |
Action | Ask your system administrator to examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | The server failed to send to or receive from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly then ask your system administrator to examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to run a deleteSet() or deleteAll() command on behalf of the remote client. |
Action | Ask your system administrator to examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | The client connection described in the message has failed a security check. |
Action | Ask your system administrator to determine why the specified client process cannot connect using the user identifier. |
Explanation | The connection described by the message failed because it referenced a messaging engine which was not available. |
Action | Ask your system administrator to determine why the messaging engine was not available. |
Explanation | A client has connected to this application server from the specified host using the specified transport chain. |
Action | None. |
Explanation | A client has disconnected from this application server. |
Action | None. |
Explanation | A messaging engine has connected to this application server from the specified host using the specified transport chain. |
Action | None |
Explanation | A messaging engine has disconnected from this application server. |
Action | None. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This is an information message. |
Action | No action required. |
Explanation | This is an information message. |
Action | No action required. |
Explanation | A channel exit running on the remote WebSphere MQ queue manager requested that channel be terminated. |
Action | Examine the error logs at the remote end of the link to see the reason why the remote exit ended the link. |
Explanation | The WebSphere MQ link may have been defined with an incorrect hostname or port number or the channel definition is missing on the remote system. |
Action | Ensure the WebSphere MQ link has been configured to connect to the correct system and that a suitable channel definition with the correct name has been defined. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The remote queue manager is not currently running. |
Action | Either start the remote queue manager or retry the operation later. |
Explanation | The remote queue manager is ending and is therefore ending all of its connections. |
Action | No action required. |
Explanation | The sequence wrap values at both ends of the link must be the same before the link can be started. |
Action | Change either end of the link to ensure the two sequence wrap values are the same and restart the link. |
Explanation | It could be that the synchronization information has become damaged or has been backed out to a previous version. If the situation can not be resolved, the sequence number can be manually reset at the sending end of the link. |
Action | Determine whether either end of the link has been restored from a previous backup or deleted and redefined. If necessary issue a RESET command to start the message sequence at a known point. |
Explanation | This is an information message. |
Action | No action required. |
Explanation | This is an information message. |
Action | No action is required. |
Explanation | Channel connections must be defined in suitable pairs. For example, a sender should connect to a receiver or requester channel. |
Action | Check the WebSphere MQ link hostname and port values to ensure that the link is configured to connect to the correct remote queue manager. Check that a suitable channel definition exists on the remote system. |
Explanation | It could be that the synchronization information has become damaged or has been backed out to a previous version. If the situation can not be resolved, the sequence number can be manually reset at the sending end of the link. |
Action | Determine whether either end of the link has been restored from a previous backup or deleted and redefined. If necessary issue a RESET command to start the message sequence at a known point. |
Explanation | The specified mq link sender channel failed to negotiate and establish a session with its partner WMQ receiver channel. The mq link sender channel stops. |
Action | Examine any other messages that are issued in addition to this one to determine, and resolve, the cause of the failure. Alternatively, ask your system administrator to capture suitable diagnostic data and to contact your local IBM Support Center. |
Explanation | A link or channel can not connect and transfer messages to a remote system if it is currently indoubt with a different system. |
Action | Either restart the link to the original system or use the RESOLVE command to resolve the indoubt. |
Explanation | The remote system refused to accept one or more messages so the link has ended. |
Action | Examine the error files and logs of the remote system to determine why the message cannot be received, and then restart the link. |
Explanation | This is an informational message. |
Action | No action is required. |
Explanation | This is an informational message. |
Action | No action is required. |
Explanation | The channel might be stopped or the remote system does not have sufficient resources to run a further channel. |
Action | Check the remote system to ensure that the channel is available to run, and retry the operation. |
Explanation | The WebSphere MQ link sender channel named in the message has started. |
Action | None. |
Explanation | The WebSphere MQ link sender channel named in the message has stopped. |
Action | None. |
Explanation | The WebSphere MQ link receiver channel named in the message has started. |
Action | None. |
Explanation | The WebSphere MQ link receiver channel named in the message has stopped. |
Action | None. |
Explanation | The WebSphere MQ connection described by the message failed because it referenced a queue manager name which did not correspond to an active WebSphere MQ link. |
Action | Ask your system administrator to determine why the WebSphere MQ link is not available. |
Explanation | The WebSphere MQ connection described by the message failed because it referenced a WebSphere MQ link channel name which did not correspond to an active WebSphere MQ link channel defined to this application server. |
Action | Ask your system administrator to determine why the WebSphere MQ link channel was not available. |
Explanation | A WebSphere MQ sender channel has connected to this application server from the specified host using the specified channel and transport chain. |
Action | None. |
Explanation | A WebSphere MQ sender channel has disconnected from this application server. |
Action | None. |
Explanation | The most likely cause of this error is if the target destination of the message exceeds the 48 character limit imposed by WebSphere MQ. |
Action | The message will have been placed on the exception destination. Check the message content, change the target destination and resend if required. |
Explanation | This is an informational message. |
Action | No action required. |
Explanation | This is an informational message. |
Action | No action required. |
Explanation | The WebSphere MQ link negotiates with the remote partner a maximum size for messages allowed down the link. Any message exceeding this value will be placed on the exception destination. |
Action | Check that the maximum message size values defined on either side of the link are sufficiently large for the configured applications. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This is an informational message. |
Action | No action required. |
Explanation | This is an informational message. |
Action | No action required. |
Explanation | This is an informational message. |
Action | No action required. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This is an informational message. |
Action | No action required. |
Explanation | This is an informational message. |
Action | No action required. |
Explanation | This is an informational message. |
Action | No action required. |
Explanation | The inbound connection request identified a channel name which is not currently configured. |
Action | Ensure that the correct receiver channel names have been used in the WebSphere MQ link definitions and that the remote partner has been configured with the correct name. |
Explanation | This message either specifies the name of the failing MQ link sender channel, or explains the nature of a WebSphere MQ link failure. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This is an informational message. |
Action | No action required. |
Explanation | During initialization of a WebSphere MQ link definition an unknown parameter was encountered. The unknown parameter will be ignored and initialization will continue. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was to start a sender channel but the specified sender channel is already running on the specified MQLink. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt to make use of a previously allocated connection to a Messaging Engine has failed because the connection has been dropped. It is possible that an MQLink or the Messaging Engine has been terminated. |
Action | Ask your system administrator to determine why the connection could have been dropped. |
Explanation | An attempt to make use of a previously allocated connection to a Messaging Engine has failed because the connection has been lost. It is possible that an MQLink or the Messaging Engine has terminated. |
Action | Ask your system administrator to determine why the connection could have been lost. |
Explanation | An MQLink has failed with some sort of internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The specified MQ link sender channel, defined in the specified MQ link, is running with the specified CCSID and is not capable of converting to the partner's CCSID. The partner receiver channel is running with the specified CCSID and is not capable of converting to the MQ link sender's CCSID. |
Action | Ensure that the sender and receiver are running with supported CCSIDs. Otherwise, ask your system administrator to capture suitable diagnostic data and to contact your local IBM Support Center. |
Explanation | The specified MQ link on the specified Bus has started. |
Action | No action required. |
Explanation | The specified MQ link on the specified Bus has stopped. |
Action | No action required. |
Explanation | The specified MQ link sender channel of the specified MQ link on the specified bus has started. |
Action | No action required. |
Explanation | The specified MQ link sender channel of the specified MQ link on the specified bus has stopped. |
Action | No action required. |
Explanation | The specified MQ link sender channel, of the specified MQ link on the specified Bus, has started. A session has been established with a partner receiver channel on the specified remote Queue Manager. |
Action | No action required. |
Explanation | The specified MQ link sender channel, of the specified MQ link on the specified Bus, has stopped. The session with the partner receiver channel on the specified remote Queue Manager has ended. |
Action | No action required. |
Explanation | The specified MQ link receiver channel, of the specified MQ link on the specified Bus, has started. |
Action | No action required. |
Explanation | The specified MQ link receiver channel, of the specified MQ link on the specified Bus, has stopped. |
Action | No action required. |
Explanation | The specified MQ link receiver channel, of the specified MQ link on the specified Bus, has started. A session has been established with the partner sender channel on the specified remote Queue Manager. |
Action | No action required. |
Explanation | The specified MQ link receiver channel, of the specified MQ link on the specified Bus, has stopped. The session with the partner sender channel on the specified remote Queue Manager has ended. |
Action | No action required. |
Explanation | A client connection with the specified user identifier was established from the specified network address. |
Action | None |
Explanation | A client connection with the specified user identifier has ended. |
Action | None |
Explanation | The specified MQLink receiver failed to put a message to the specified target queue. The target queue may be full, disabled for sends, undefined, or an attempt to create a producer session against it has failed for some reason. |
Action | If the queue is full, process messages on the queue, if it is not enabled for sends, or if it is not defined, ask your system administrator to enable or define it, respectively. Alternatively, ask your system administrator to capture suitable diagnostic data and to contact your local IBM Support Center. |
Explanation | An attempt was made to create an Object Store with a negative initial size. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to create an Object Store with a negative maximum size. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to create an Object Store with an initial size that was less than the origin of the Object Store. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to create an Object Store with an initial size that was greater than the maximum size. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to retrieve an object from the Object Store, but an object version mismatch was encountered. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made remove an object from the Object Store, but an object version mismatch was encountered. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to locate an object in the Object Store, but the supplied object index was found to be less than the origin of the Object Store. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to locate an object in the Object Store, but no suitable object was found for the supplied object index. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to remove an object from the Object Store, but the supplied object index was found to be less than the origin of the Object Store. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to remove an object from the Object Store, but no suitable object was found for the supplied object index. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made dump entries in the Object Store, but the supplied number of entries to be dumped was found to be negative. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | During initialization of an MQClientLink object, an unknown parameter was encountered. The unknown parameter will be ignored and initialization will continue. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The WebSphere MQ connection described in the message has failed a security check. |
Action | Ask your system administrator to determine why the specified WebSphere MQ process cannot connect using the user identifier. |
Explanation | The WebSphere MQ connection described by the message failed because it referenced a queue manager name which did not correspond to an active MQClientLink. |
Action | Ask your system administrator to determine why the MQClientLink is not available. |
Explanation | The WebSphere MQ connection described by the message failed because it referenced a channel name which did not correspond to the channel parameter in the named MQClientLink. |
Action | Ask your system administrator to determine what the correct channel name should be. |
Explanation | A WebSphere MQ client application has connected to this application server from the specified host using the specified transport chain. |
Action | None |
Explanation | A WebSphere MQ client has disconnected from this application server. |
Action | None. |
Explanation | While processing a request for connection from a client, the Messaging Engine associated with an SICoreConnection object could not be found. It is possible that the Messaging Engine has terminated, or is no longer a member of the bus, and hence the connection has been lost. |
Action | Ask your system administrator to determine why the Messaging engine is no longer available. |
Explanation | An attempt to make use of a previously allocated connection to a Messaging Engine has failed because the connection has been dropped. It is possible that client or Messaging Engine has terminated. |
Action | Restart the client or Messaging Engine if required, otherwise ask your system administrator to determine why the connection could have been dropped. |
Explanation | An attempt to make use of a previously allocated connection to a Messaging Engine has failed because the connection has been lost. It is possible that client or Messaging Engine has terminated. |
Action | Restart the client or Messaging Engine if required, otherwise ask your system administrator to determine why the connection could have been lost. |
Explanation | An MQClientLink has failed with some sort of internal error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The client received some data over multicast, but the data appears to be corrupt and cannot be parsed. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Examine the cause of the connection failure to see if it helps to diagnose the problem and retry the operation. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A remote call was made to the core API that generated an exception. However, the exception was not recognized or expected at this time. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A method call was made on the client that should only be called on the server. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to set a property but the value supplied was incorrect for the property. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to encode a string using a specified encoding, but this failed because the encoding was unsupported. |
Action | Correct the encoding value and repeat the operation. |
Explanation | The string cannot be sent across the network using JFAP as the length exceeds the JFAP limit. |
Action | Correct the string to reduce its length and repeat the operation. |
Explanation | The remote server generated an exception that caused an FFDC. |
Action | Examine the exception and the corresponding FFDC file on the server to determine the problem and retry your operation. |
Explanation | An attempt was made to set a property but the value supplied was incorrect for the property. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Handshaking information was received that was not understand. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The messaging engine handshake has failed due to an incorrect property. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to set a property but the value supplied was incorrect for the property. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The client handshake has failed due to an incorrect property. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to set a property but the value supplied was incorrect for the property. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to set a property but the value supplied was incorrect for the property. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A client connection with the specified user identifier was established from the specified network address. |
Action | None |
Explanation | A client connection with the specified user identifier has ended. |
Action | None |
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. |