Express (Distributed operating systems), v8.0 > Reference > Messages
CWSIC
CWSIC0001E: An internal error occurred. An object of class ServerTransportFactory cannot be created because of exception: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC0002E: An internal error occurred. An object of class ClientConnectionFactoryImpl cannot be created because of exception: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC0003E: An internal error occurred. An object of class MEConnectionFactoryImpl cannot be created because of exception: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC0004E: An internal error occurred. A null endpoint was passed as an argument.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC0005E: An internal error occurred. A null chain name was passed as an argument.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC0006E: An internal error occurred. The wrong method was called for this object type.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC0065E: An operation was attempted on a connection that is already closed.
Explanation An operation was attempted on a connection resource that has previously been closed. This problem can result from an application programming error or because the system closed the connection resource in response to detecting an error condition. Action Examine the log files for your application server to determine why the connection was closed. See the accompanying error messages for further information. Correct the problem if possible.
CWSIC0068E: An operation was attempted on a connection that is already closed.
Explanation An operation was attempted on a connection resource that has previously been closed. This problem can result from an application programming error or because the system closed the connection resource in response to detecting an error condition. Action Examine the log files for your application server to determine why the connection was closed. See the accompanying error messages for further information. Correct the problem if possible.
CWSIC0101E: An internal error occurred. A call was attempted but this is not valid at FAP level {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1001E: A client attempted to connect with a remote messaging engine ({1}) but the connection cannot be completed. Ensure the messaging engine is started: exception {0}.
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.
CWSIC1003E: An internal error occurred. An object of class JsMessage cannot be created because of exception {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1004E: An internal error occurred. An object of class DestinationConfigurationFactory cannot be created because of exception {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1005E: An internal error occurred. An object of class CompHandshake cannot be created because of exception {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1006E: An internal error occurred. An unexpected reply {1} was received, expected reply was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1008E: An internal error occurred. No conversation is available.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1009E: An attempt was made to register a null asynchronous consumer callback.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1010E: An internal error occurred. A protocol error has occurred. Unexpected data was received from the server ({1}). The data ID was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1011E: An internal error occurred. The proxy conversation group cannot be retrieved.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1012E: An internal error occurred. The proxy queue on which a received asynchronous message should be placed cannot be located.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1013E: An attempt was made to use a closed session object.
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.
CWSIC1014E: An attempt was made to use a closed connection object.
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.
CWSIC1015E: An attempt was made to register or deregister an asynchronous consumer callback for a consumer session that is started.
Explanation An attempt was made to register or unregister 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 unregister an asynchronous consumer callback.
CWSIC1016E: An attempt was made to register a null asynchronous consumer callback.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1017E: An attempt was made to unlock an incorrect message.
Explanation An attempt was made to unlock an incorrect message in a locked message enumeration. Action Before invoking the unlock method, make sure the locked message enumeration cursor is positioned on a message for which the unlock operation is valid.
CWSIC1018E: An attempt was made to delete an incorrect message.
Explanation An attempt was made to delete an incorrect message in a locked message enumeration. Action Before invoking the delete method, make sure the locked message enumeration cursor is positioned on a message for which the delete operation is valid.
CWSIC1019E: The maximum number of open sessions has been reached. The maximum permitted number of open sessions is {0}.
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.
CWSIC1020E: An attempt has been made to invoke a synchronous method whilst an asynchronous consumer is registered.
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.
CWSIC1021E: An attempt has been made to invoke method {0}, which is not valid on the client.
Explanation The invoked method is valid only on an in-process client and is not allowed to be called from a remote client. Action More info at:
CWSIC1022E: An attempt has been made to call a method on a transaction object when the transaction has already been committed or rolled back.
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.
CWSIC1023E: Client connection was not successful because the remote server ({0}) is not able to support this client.
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.
CWSIC1024E: The user information supplied was rejected by the server when authentication was attempted: exception {0}.
Explanation When attempting to log in, the server rejected the user information supplied. Action Ensure the user information is correct and try again.
CWSIC1025E: An internal error occurred. An error occurred when closing a proxy queue conversation group. The first exception was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1026E: An internal error occurred. The server informed the client to use multicast for the consumer session, but this was not requested.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1029E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1030E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1031E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1032E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1033E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1034E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1035E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1036E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1037E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1038E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1039E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1040E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1041E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1042E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1043E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1044E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1045E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1046E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1048E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1049E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1050E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1051E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1052E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1053E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1054E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1055E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1056E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1057E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1058E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1059E: An attempt was made to use a closed connection object.
Explanation A method was invoked on a connection that has already been closed. Action Ensure that the method call is performed before the connection is closed.
CWSIC1060E: An attempt was made to invoke a receive() method whilst another receive() method is still in-progres.
Explanation Only one receive() can be in progress at any one time per consumer session. Action Ensure that only one receive method is called at a time on a consumer session.
CWSIC1061E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1062E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1063E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC1066E: An attempt has been made to call a method on a transaction object when the transaction has already been committed or rolled back.
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.
CWSIC1067E: An attempt has been made to call a method on a transaction object when the transaction has already been committed or rolled back.
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.
CWSIC2001I: Messaging connections are being accepted.
Explanation This application server is now accepting messaging connection requests from clients and other messaging engines. Action No action is required.
CWSIC2002E: The server cannot unlock messages that are currently locked on behalf of the remote client: exception {0}.
Explanation The server failed to run an unlockSet() command on behalf of the remote client. Action Examine the error and FFDC logs to help determine the reason for the problem.
CWSIC2003E: An internal error occurred. An incorrect call was made to the main consumer class.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2004E: The messaging engine cannot listen for remote connections: exception {0}.
Explanation The server transport failed to initialize. The messaging engine may not be able to accept remote connections. Action Examine the error and FFDC logs to help determine the reason for the problem.
CWSIC2005E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2006E: The server cannot unlock messages that are currently locked on behalf of the remote client: exception {0}.
Explanation The server failed to run an unlockSet() command on behalf of the remote client. Action Examine the error and FFDC logs to help determine the reason for the problem.
CWSIC2007E: The server cannot delete messages that are currently locked on behalf of the remote client: exception {0}.
Explanation The server failed to run a deleteSet() or deleteAll() command on behalf of the remote client. Action Examine the error and FFDC logs to help determine the reason for the problem.
CWSIC2008E: This transaction cannot commit as an operation that was performed within the transaction boundary failed. The first operation that failed generated the following exception: {0}.
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 a FFDC record was generated to help you diagnose the cause of the failure. Action Examine the error and FFDC logs to help determine the reason for the problem.
CWSIC2009E: There was a failure to send a message: exception {0}.
Explanation It was not possible to send a transacted or non-reliable message due to the stated exception. Action Examine the error and FFDC logs to help determine the reason for the problem.
CWSIC2010E: An internal error occurred. It is not possible to store an object in the object store: exception {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2011E: There is an internal error; it is not possible to relinquish control to a subordinate conversation listener.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2012E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2013E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2014E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2015E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2016E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2017E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2018E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2019E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2020E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2021E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2022E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2023E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2024E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2025E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2026E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2027E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2028E: The server cannot delete messages that are currently locked on behalf of the remote client: exception {0}.
Explanation The server failed to run a deleteSet() or deleteAll() command on behalf of the remote client. Action Examine the error and FFDC logs to help determine the cause of the problem.
CWSIC2029E: This transaction cannot commit as an operation that was performed within the transaction boundary failed. The first operation that failed generated the following exception: {0}.
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 a FFDC record was generated to help you diagnose the cause of the failure. Action Examine the error and FFDC logs to help determine the cause of the problem.
CWSIC2030W: The messaging engine connection to host {0} on port {1} using chain {2} has been closed.
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. Examine the error and FFDC logs to help determine the cause of the problem.
CWSIC2032E: The server cannot unlock messages that are currently locked on behalf of the remote client: exception {0}.
Explanation The server failed to run an unlockSet() command on behalf of the remote client. Action Examine the error and FFDC logs to help determine the reason for the problem.
CWSIC2033E: A communication error occurred when sending to or receiving from a remote client: exception {0}.
Explanation The server failed to send data to or receive data 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, examine the error and FFDC logs to help determine the reason for this problem.
CWSIC2034E: The server cannot delete messages that are currently locked on behalf of the remote client: exception {0}.
Explanation The server failed to run a deleteSet() or deleteAll() command on behalf of the remote client. Action Examine the error and FFDC logs to help determine the reason for the problem.
CWSIC2035E: A client connection attempt from host {0} on transport chain {1} using a user identifier of {2} failed to be authenticated.
Explanation The client connection described in the message has failed a security check. Action Examine the error logs to determine why the specified client process cannot connect using the user identifier.
CWSIC2036E: A connection attempt from host {0} on transport chain {1} failed because the messaging engine requested, {2} on bus {3}, does not correspond to an active messaging engine which is available to this application server.
Explanation The connection described by the message failed because it referenced a messaging engine which was not available. Action Examine the error logs to determine why the messaging engine was not available.
CWSIC2041E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2042E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2043E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2044E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2045E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2046E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2047E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2048E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2049E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2050E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2051E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2052E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2053E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2054E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2055E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2056E: A message schema was requested by a client but the schema could not be located.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2057E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2058E: An internal error occurred. An attempt was made to save an object in the map with id {0}, but there already exists an item in the map with this key.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2059E: An internal error occurred. An attempt was made to get an object from the map with id {0}, but there is no item in the map with this key.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2060E: An internal error occurred. An attempt to use a transaction was prohibited possibly because it failed to be created successfully.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2161E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2162E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2163E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC2164E: An operation was attempted on a connection that is already closed.
Explanation An operation was attempted on a connection resource that has previously been closed. This problem can result from an internal error or because the system closed the connection resource in response to detecting an error condition. Action Examine the log files for your application server to determine why the connection was closed. See the accompanying error messages for further information and correct the problem if possible.
CWSIC2165E: An internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC3001I: WebSphere MQ link {0} ended normally.
Explanation This is an information message. Action No action is required.
CWSIC3002I: WebSphere MQ link {0} started.
Explanation This is an information message. Action No action is required.
CWSIC3005E: WebSphere MQ link {0} ended because the channel exit on remote system {1} requested it.
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 determine why the remote exit ended the link.
CWSIC3006E: The WebSphere MQ link {0} ended because channel {1} is not currently available on the remote system.
Explanation The WebSphere MQ link may have been defined with an incorrect host name 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.
CWSIC3007E: An internal error occurred. During communication through WebSphere MQ link {0} the remote queue manager channel program detected a protocol error. The failure type was {1} with associated data of {2}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC3008E: WebSphere MQ link {0} cannot start because the remote queue manager is not currently available.
Explanation The remote queue manager is not currently running. Action Either start the remote queue manager or retry the operation later.
CWSIC3009I: WebSphere MQ link {0} is closing because the remote queue manager is ending.
Explanation The remote queue manager is ending and is therefore ending all of its connections. Action No action is required.
CWSIC3010E: The sequence number wrap value for WebSphere MQ link {0} is {1}, but the value specified at the remote location is {2}. The two values must be the same before the channel can be started.
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.
CWSIC3011E: The WebSphere MQ link {0} and the remote queue manager do not agree on the next message sequence number. A message with sequence number {1} has been sent when sequence number {2} was expected.
Explanation It could be that the synchronization information has become damaged or has been backed out to a previous version. If the situation cannot 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 at the sending end to start the message sequence at a known point.
CWSIC3012I: The WebSphere MQ link {0} is closing because of a request by the user.
Explanation This is an information message. Action No action is required.
CWSIC3013I: The WebSphere MQ link sender {0} has ended because no messages arrived for transmission within the disconnect interval period.
Explanation This is an information message. Action No action is required.
CWSIC3014E: The WebSphere MQ link {0} is ending because channel {1} on the remote machine is not of a suitable type.
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 host name 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.
CWSIC3015E: The WebSphere MQ link {0} and the remote queue manager do not agree on the next message sequence number. A message with sequence number {1} has been received when sequence number {2} was expected.
Explanation It could be that the synchronization information has become damaged or has been backed out to a previous version. If the situation cannot 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.
CWSIC3062E: Channel negotiation failed for MQ link sender {0}, defined in MQ link {1}. MQ link sender stopping.
Explanation The specified MQ link sender channel failed to negotiate and establish a session with its partner WebSphere MQ receiver channel. The MQ link sender channel stops. Action Examine the accompanying error messages to determine and resolve the cause of the failure. Alternatively, capture suitable diagnostic data and contact your local IBM Support Center.
CWSIC3065E: The WebSphere MQ link {0} can not start because it is currently indoubt over channel {1} with queue manager {2}.
Explanation A link or channel cannot 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.
CWSIC3080E: The WebSphere MQ link {0} has ended because the remote queue manager {1} cannot receive a message.
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.
CWSIC3096I: While sending message to queue manager {1} down WebSphere MQ link {0} one or more messages were sent to the exception destination.
Explanation Informational message. Action Check the message content of messages on the exception destination to determine why the messages were placed there. Use this information to resolve the problem.
CWSIC3097I: While sending messages to queue manager {0} down WebSphere MQ link {1}, one or more messages were sent to an exception destination.
Explanation Informational message. Action Examine the logs for associated error messages that may provide details of the exception destination to which the undelivered messages were sent. Check the content of these messages to determine why they were placed there. Use this information to resolve the problem.
CWSIC3098I: While receiving message from queue manager {1} down WebSphere MQ link {0} one or more messages were sent to the exception destination.
Explanation Informational message. Action Check the message content of messages on the exception destination to determine why the messages were placed there. Use this information to resolve the problem.
CWSIC3099I: While receiving messages from queue manager {0} down WebSphere MQ link {1} one or more messages were sent to an exception destination.
Explanation Informational message. Action Examine the logs for associated error messages that may provide details of the exception destination to which the undelivered messages were sent. Check the content of these messages to determine why they were placed there. Use this information to resolve the problem.
CWSIC3108E: The WebSphere MQ link {0} ended because channel {1} is not currently available on the remote system.
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.
CWSIC3109I: The sender channel {0} for WebSphere MQ link {1} has started.
Explanation The WebSphere MQ link sender channel named in the message has started. Action No action is required.
CWSIC3110I: The sender channel {0} for WebSphere MQ link {1} has stopped.
Explanation The WebSphere MQ link sender channel named in the message has stopped. Action No action is required.
CWSIC3111I: The receiver channel {0} for WebSphere MQ link {1} has started.
Explanation The WebSphere MQ link receiver channel named in the message has started. Action No action is required.
CWSIC3112I: The receiver channel {0} for WebSphere MQ link {1} has stopped.
Explanation The WebSphere MQ link receiver channel named in the message has stopped. Action No action is required.
CWSIC3115I: A WebSphere MQ sender channel {0} from host {1} has established a connection on transport chain {2}.
Explanation A WebSphere MQ sender channel has connected to this application server from the specified host using the specified channel and transport chain. Action No action is required.
CWSIC3116I: A WebSphere MQ sender channel {0}, previously connected from host {1} on transport chain {2}, has disconnected.
Explanation A WebSphere MQ sender channel has disconnected from this application server. Action No action is required.
CWSIC3117E: An attempt was made to connect to WebSphere Messaging using MQ Client Link {0} but this could not be completed because the transport chain {1} is not permitted by the security configuration of bus {2}.
Explanation The bus is configured to only allow connections through particular transport chains and this connection could not complete because the chain was not permitted. Action Connect through a different transport chain, or configure the bus to allow connections through this chain.
CWSIC3118E: An attempt was made to connect to WebSphere Messaging using MQ Link {0} but this could not be completed because the transport chain {1} is not permitted by the security configuration of bus {2}.
Explanation The bus is configured to only allow connections through particular transport chains and this connection could not complete because the chain was not permitted. Action Connect through a different transport chain, or configure the bus to allow connections through this chain.
CWSIC3119E: An attempt was made to connect to WebSphere MQ using MQ Link {0} but this could not be completed because the transport chain {1} is not permitted by the security configuration of bus {2}.
Explanation The bus is configured to only allow connections through particular transport chains and this connection could not complete because the chain was not permitted. Action Connect through a different transport chain, or configure the bus to allow connections through this chain.
CWSIC3200E: The WebSphere MQ link {0} could not transmit a message because it was not a valid format for WebSphere MQ.
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 an exception destination. Check the message content to resolve the problem.
CWSIC3201I: The sender channel {0} for WebSphere MQ link {1} has been requested to start.
Explanation Informational message. Action No action is required.
CWSIC3202I: The sending side of the WebSphere MQ link {0} has been requested to stop.
Explanation Informational message. Action No action is required.
CWSIC3205E: The encoded message is too big to be sent down WebSphere MQ link {0}. The message size is {1}, but the maximum message size is {2}. An attempt will be made to place the message on to the exception destination.
Explanation The WebSphere MQ link negotiates with the remote partner a maximum size for messages allowed down the link. If the size of a message exceeds this value, an attempt will be made to place the message on to the exception destination. Action Check that the maximum message size values defined at either side of the link are sufficiently large for the configured applications.
CWSIC3206E: The encoded message is too big to be sent down WebSphere MQ link {0}. The message size is {1}, but the maximum message size is {2}. An attempt will be made to send the message to an exception destination.
Explanation The WebSphere MQ link negotiates with the remote partner a maximum size for messages allowed down the link. If the size of a message to be sent exceeds this maximum size, an attempt is made to send the message to an exception destination. Action Examine the logs for associated error messages that may provide details of the exception destination to which the undelivered messages were sent. Examine the undelivered message if required, and ensure that the maximum message size values defined at either side of the link are sufficiently large for the configured applications.
CWSIC3209E: An internal error occurred. During processing of WebSphere MQ link {0} a request to move to invalid state {1} was received.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC3212E: The sending side of WebSphere MQ link {0} received invalid data and will end. The invalid data buffer was {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC3213E: An internal error occurred. During processing of WebSphere MQ link {0} an illegal state transition from state {1} to state {2} was attempted.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC3214E: The sender channel {0} of WebSphere MQ link {1} has an invalid connection name list {2}.
Explanation The connection information in the connection name list is used to establish a connection with a WebSphere MQ queue manager. The connection name list provided is not valid. Action Ensure a valid connection name list is given. Refer to the WAS Information Center for the valid syntax for a connection name list.
CWSIC3220I: The receiver channel {0} for WebSphere MQ link {1} has been requested to start.
Explanation Informational message. Action No action is required.
CWSIC3221I: The receiving side of the WebSphere MQ link {0} has been requested to stop.
Explanation Informational message. Action No action required.
CWSIC3222I: WebSphere MQ link {0} from address {1} has been adopted.
Explanation Informational message. Action No action is required.
CWSIC3223E: An internal error occurred. During processing of the receiving side of WebSphere MQ link {0} an illegal state transition from state {1} to state {2} was attempted.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC3228E: The target publish subscribe bridge destination {0} is undefined. It is possible that a message has been received for an old subscription request and clean up may be necessary.
Explanation The message was probably for a subscription request that has since terminated. Hence, the target destination is no longer available and the recoverable message cannot be delivered. Action Refer to the WAS Information Center for details on how to clean up old subscriptions.
CWSIC3229I: The target publish subscribe bridge destination {0} is undefined. It is possible that a message has been received for an old subscription request and clean up may be necessary. Non-recoverable messages destined for this destination have been discarded.
Explanation The message was probably for a subscription request that has since terminated. Hence, the target destination is no longer available. Non-recoverable messages cannot be delivered and have been discarded. Action Refer to the WAS Information Center for details of how to clean up old subscriptions.
CWSIC3230E: An error occurred trying to send a message to an exception destination.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC3231E: An error occurred trying to send a message to the exception destination.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC3232I: WebSphere MQ link {0} ended normally.
Explanation Informational message. Action No action is required.
CWSIC3233I: WebSphere MQ link {0} manually resolved for commit by user request.
Explanation Informational message. Action No action is required.
CWSIC3234I: WebSphere MQ link {0} manually resolved for back out by user request.
Explanation Informational message. Action No action is required.
CWSIC3236E: WebSphere MQ link is rejecting a connection because a link definition for channel {0} does not exist.
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 in its channel definition.
CWSIC3237E: There is a WebSphere MQ link failure: {0}.
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 More info at:
CWSIC3239E: There is an illegal segment type error {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC3240I: WebSphere MQ link {0} reset on user request.
Explanation Informational message. Action No action is required.
CWSIC3242I: An internal error occurred. Unknown WebSphere MQ link parameter {0} with value {1}.
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 More info at:
CWSIC3243I: Sender channel {0} is already running on MQ link {1}.
Explanation An attempt was made to start a sender channel but the specified sender channel is already running on the specified MQ link. Action More info at:
CWSIC3244E: A connection to Messaging Engine {0} has been dropped.
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 MQ link or the messaging engine has been terminated. Action Examine the error logs to determine why the connection could have been dropped.
CWSIC3245E: A connection to Messaging Engine {0} has been lost.
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 MQ link or the messaging engine has terminated. Action Examine the error logs to determine why the connection could have been lost.
CWSIC3246E: MQ link {0} has encountered an internal error.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC3247E: An MQ link sender channel is unable to encode and deliver a message to queue {0} at queue manager {1}. The local bus is {2} and the foreign bus is {3}. The associated exception is {4}.
Explanation An MQ link sender channel has failed to encode a message destined for the specified queue and queue manager names so the message cannot be delivered to the target destination. The local and foreign bus names, as well as the associated exception, are also given. It is possible that some sort of internal error has occurred. Since the message cannot be formatted, it is possible that some names are not available. In which case, a value of ' <unknown>' appears in the message text. Action Examine any other messages that are issued in addition to this one to determine, and resolve, the cause of the failure. Alternatively, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3248I: The MQ link sender channel {0}, defined in MQ link {1}, has received an error flow from the partner receiver channel.
Explanation The specified MQ link sender channel, defined in the specified MQ link, has received an error flow from the partner receiver channel. The MQ link sender may stop. Action It is possible that the partner receiver channel has been stopped so this could be normal behaviour. Examine any other messages in the Application Server logs, or in the WebSphere MQ AMQERR* log files, to determine if there is a failure, and resolve the cause of the failure. Alternatively, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3249E: The MQ link sender channel {0}, defined in MQ link {1}, has received an unexpected error. The error return code is {2}.
Explanation The specified MQ link sender channel, defined in the specified MQ link, has received an unexpected error from the partner receiver channel. The MQ link sender may stop. Action For further information on resolving this error, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3250E: Unsupported CCSID. The MQ link sender channel {0}, defined in MQ link {1}, is running with CCSID {2} while the partner receiver channel is running with CCSID {3}.
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. Alternatively, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3251E: Security failure. The MQ link sender channel {0}, defined in MQ link {1}, has received an error flow from its partner indicating that an authorization failure has occurred.
Explanation The specified MQ link sender channel, defined in the specified MQ link, has received an error flow indicating that an authorization failure has occurred. Action Ensure that the specified MQ link sender channel and its target WebSphere MQ receiver channel have matching security configuration parameters. Also examine the logs from either end of the channel in order to determine the cause of the failure. Alternatively, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3252E: Security failure. The MQ link sender channel {0}, defined in MQ link {1}, has received an error flow from its partner indicating that a security error has occurred because the CipherSpec values specified at the two ends of the channel do not match, or because an incorrect CipherSpec value has been specified.
Explanation The specified MQ link sender channel, defined in the specified MQ link, has received an error flow (indicating that a security error has occurred) because CipherSpec values specified at the two ends of the channel do not match, or because an incorrect CipherSpec value has been specified. Action Ensure that the specified MQ link sender channel and its target WebSphere MQ receiver channel have matching security configuration parameters. Also examine the logs from either end of the channel in order to determine the cause of the failure. Alternatively, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3253E: Security failure. The MQ link sender channel {0}, defined in MQ link {1}, has received an error flow from its partner indicating that a security error has occurred because the peer name specified on the channel definition does not match the Distinguished Name in the certificate supplied, or is incorrect.
Explanation The specified MQ link sender channel, defined in the specified MQ link, has received an error flow indicating that the peer name specified on the channel definition does not match the Distinguished Name in the certificate supplied, or is incorrect. Action Ensure that the specified MQ link sender channel and its target WebSphere MQ receiver channel have matching security configuration parameters. Also examine the logs from either end of the channel in order to determine the cause of the failure. Alternatively, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3254E: Security failure. The MQ link sender channel {0}, defined in MQ link {1}, has received an error flow from its partner indicating that a security error has occurred because no certificate was provided when one was expected due to SSL being enabled.
Explanation The specified MQ link sender channel, defined in the specified MQ link, has received an error flow indicating no certificate was provided when one was expected due to SSL being enabled. Action Ensure that the specified MQ link sender channel and its target WebSphere MQ receiver channel have matching security configuration parameters. Also examine the logs from either end of the channel in order to determine the cause of the failure. Alternatively, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3260W: The MQ link sender channel {0}, defined in MQ link {1}, couldn''t send a message to the default exception destination.
Explanation The specified MQ link sender channel, defined in the specified MQ link, couldn't send a message to the default exception destination. Action Check whether a default exception destination has been configured and if desired configure one. Alternatively, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3261W: The MQ link sender channel {0}, defined in MQ link {1}, couldn''t send a message to an exception destination.
Explanation The specified MQ link sender channel, defined in the specified MQ link, couldn't send a message to an exception destination. Action Examine the logs for associated error messages that may provide details of the exception destination to which the undelivered message could not be sent. Ensure that a default, or link specific, exception destination is configured. If an exception destination is already configured, ensure that it is not full or disabled for sends. Alternatively, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3300I: MQ link {0} on bus {1} started.
Explanation The specified MQ link on the specified bus has started. Action No action is required.
CWSIC3301I: MQ link {0} on bus {1} stopped.
Explanation The specified MQ link on the specified bus has stopped. Action No action is required.
CWSIC3302I: MQ link sender channel {0}, of MQ link {1} on Bus {2}, started.
Explanation The specified MQ link sender channel of the specified MQ link on the specified bus has started. Action No action is required.
CWSIC3303I: MQ link sender channel {0}, of MQ link {1} on Bus {2}, stopped.
Explanation The specified MQ link sender channel of the specified MQ link on the specified bus has stopped. Action No action is required.
CWSIC3304I: MQ link sender channel {0}, of MQ link {1} on Bus {2}, to Queue Manager {3} started.
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 is required.
CWSIC3305I: MQ link sender {0}, of MQ link {1} on Bus {2}, to Queue Manager {3} stopped.
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 is required.
CWSIC3306I: MQ link receiver channel {0}, of MQ link {1} on Bus {2}, started.
Explanation The specified MQ link receiver channel, of the specified MQ link on the specified bus, has started. Action No action is required.
CWSIC3307I: MQ link receiver channel {0}, of MQ link {1} on Bus {2}, stopped.
Explanation The specified MQ link receiver channel, of the specified MQ link on the specified bus, has stopped. Action No action is required.
CWSIC3308I: MQ link receiver channel {0}, of MQ link {1} on Bus {2}, from Queue Manager {3} started.
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 is required.
CWSIC3309I: MQ link receiver channel {0}, of MQ link {1} on Bus {2}, from Queue Manager {3} stopped.
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 is required.
CWSIC3310I: Client {0} connection started from {1}.
Explanation A client connection with the specified user identifier was established from the specified network address. Action No action is required.
CWSIC3311I: Client {0} disconnected.
Explanation A client connection with the specified user identifier has ended. Action No action is required.
CWSIC3312I: MQ link receiver {0} failed to send a message to target queue {1}, on messaging engine {2}. See associated message {3}.
Explanation The specified MQ link receiver failed to send 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 Process messages on the queue if it is full. If the queue is not configured to allow messages to be sent to it, or if it is not defined, reconfigure it or define it, respectively. Alternatively,see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3313I: MQ link sender {0} failed to start because the associated foreign bus {1} with UUID {2} could not be located.
Explanation The specified MQ link sender was unable to start because the associated foreign bus could not be located. The MQ link will not be started. Action Examine your MQ link sender configuration and ensure it is associated with a valid foreign bus.
CWSIC3314E: An Unsupported CCSID {0} has been encountered during an inbound connection request from a WebSphere MQ sender channel or a client.
Explanation The specified CCSID, supplied in an inbound connection request from a WebSphere MQ sender channel or a client, is unsupported. Action Run with a supported CCSID. It is possible that the JVM that you are running with does not support the supplied CCSID.
CWSIC3350I: The system administrator has changed the configuration of WebSphere MQ link {0}.
Explanation Informational message. Action No action required.
CWSIC3351I: The system administrator has initiated deletion of WebSphere MQ link {0}.
Explanation Informational message. Action No action is required.
CWSIC3352I: Deletion of WebSphere MQ link {0} has successfully completed.
Explanation Informational message. Action No action is required.
CWSIC3353I: The {0} running instances of WebSphere MQ link receiver channel {1} have been stopped because the system administrator has modified the configuration of WebSphere MQ link {2}.
Explanation The system administrator has either changed the name of the WebSphere MQ link receiver channel, or has deleted the WebSphere MQ link receiver channel, hence the running instances of the WebSphere MQ link receiver channel have been stopped. Action It is possible that no action is required. However, the associated partner WebSphere MQ sender channel(s) might have been left in an indoubt state, in which case resolve the indoubt channels appropriately.
CWSIC3354I: The {0} running instances of WebSphere MQ link receiver channel {1} have been stopped because the system administrator has modified the configuration of WebSphere MQ link {2}.
Explanation The system administrator has either changed the name of the WebSphere MQ link receiver channel, or has deleted the WebSphere MQ link receiver channel, hence the running instances of the WebSphere MQ link receiver channel have been stopped. Action It is possible that no action is required. However, the associated partner WebSphere MQ sender channel(s) might have been left in an indoubt state, in which case resolve the indoubt channels appropriately.
CWSIC3355I: The system administrator has changed the configuration of WebSphere MQ link {0} but the {1} running WebSphere MQ link receiver instances for this link will not be affected by this change.
Explanation WebSphere MQ link receiver instances only pick up configuration settings when starting up. Thus any configuration changes made to a running WebSphere MQ link will not effect running WebSphere MQ link receiver instances. Action If you wish the running WebSphere MQ link receiver instances to use the latest configuration changes then they either need to all be stopped before the changes are made, or they need to be stopped and restarted to pick up the changed configuration.
CWSIC3356I: The system administrator has changed the configuration of WebSphere MQ link {0} which affects the running WebSphere MQ link sender {1}. The changes will only be picked up when the WebSphere MQ link sender goes through starting state or has been explicitly stopped and restarted.
Explanation WebSphere MQ link senders pick up most configuration settings when going through the starting state. Thus, if a configuration change occurs, the changes are only picked up when the WebSphere MQ link sender next enters the starting state. This can be achieved by administratively stopping and starting the WebSphere MQ link sender, or changes will be picked up when the WebSphere MQ link sender next enters the starting state, perhaps due to retries occurring or the disconnect interval being reached. Action If you want the WebSphere MQ link sender to use the latest configuration changes, either stop the MQ link sender before making the changes, or stop and restart the MQ link sender to pick up the new configuration.
CWSIC3357I: The running WebSphere MQ link sender {0} has been stopped because the system administrator has modified the configuration of WebSphere MQ link {1}.
Explanation The system administrator has either changed the name of the WebSphere MQ link sender, or has deleted the WebSphere MQ link sender. Hence the running WebSphere MQ link sender has been stopped. Action It is possible that no action is required. However, the deleted WebSphere MQ link sender may now be in an indoubt state and so may need to be resolved.
CWSIC3358W: Deletion of WebSphere MQ link {0} has not been successfully completed as WebSphere MQ link sender {1} is in an indoubt state.
Explanation The configuration for the named WebSphere MQ link has been deleted, but the named WebSphere MQ link sender is still in an indoubt state. The deletion cannot fully complete until the indoubt state is resolved. Action Use the administrative tooling to resolve the indoubt state which will allow the deletion of the named WebSphere MQ link to complete.
CWSIC3500E: An internal error occurred. An incorrect value was supplied for the initial size of the Object Store. The initial size was {0}.
Explanation An attempt was made to create an Object Store with a negative initial size. Action More info at:
CWSIC3501E: An internal error occurred. An incorrect value was supplied for the maximum size of the Object Store. The maximum size was {0}.
Explanation An attempt was made to create an Object Store with a negative maximum size. Action More info at:
CWSIC3502E: An internal error occurred. An incorrect value was supplied for the initial size of the Object Store. The initial size was {0}. The origin of the Object Store was {1}.
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 More info at:
CWSIC3503E: An internal error occurred. An incorrect value was supplied for the initial size of the Object Store. The initial size was {0}. The maximum size was {1}.
Explanation An attempt was made to create an Object Store with an initial size that was greater than the maximum size. Action More info at:
CWSIC3504E: An internal error occurred. The supplied object version is found to be different to that of the object stored in the Object Store. The supplied object version was {0}. The object version in the Object Store was {1}.
Explanation An attempt was made to retrieve an object from the Object Store, but an object version mismatch was encountered. Action More info at:
CWSIC3505E: An internal error occurred. The supplied object version is found to be different to that of the object stored in the Object Store. The supplied version was {0}. The version in the Object Store was {1}.
Explanation An attempt was made to remove an object from the Object Store, but an object version mismatch was encountered. Action More info at:
CWSIC3506E: An internal error occurred. An incorrect value was supplied for the index of an object in the Object Store. The supplied index was {0}. The origin of the Object Store was {1}.
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 More info at:
CWSIC3507E: An internal error occurred. An incorrect value was supplied for the index of an object in the Object Store. The supplied index was {0}.
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 More info at:
CWSIC3508E: An internal error occurred. An incorrect value was supplied for the index of an object in the Object Store. The supplied index was {0}. The origin of the Object Store was {1}.
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 More info at:
CWSIC3509E: An internal error occurred. An incorrect value was supplied for the index of an object in the Object Store. The supplied index was {0}.
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 More info at:
CWSIC3510E: An internal error occurred. An incorrect value was supplied for the number of entries to be dumped from the Object Store. The number of entries specified was {0}.
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 More info at:
CWSIC3620I: The indoubt batch of messages for WebSphere MQ link {0} could not be rolled back as the WebSphere MQ link sender with channel name {1} is not stopped.
Explanation An attempt was made to rollback an indoubt batch of messages while the stated WebSphere MQ link sender was still running. Action Stop the stated WebSphere MQ link sender and repeat the action.
CWSIC3621I: The indoubt batch of messages for WebSphere MQ link {0} could not be committed as the WebSphere MQ link sender with channel name {1} is not stopped.
Explanation An attempt was made to commit an indoubt batch of messages when the stated WebSphere MQ link sender was still running. Action Stop the stated WebSphere MQ link sender and repeat the action.
CWSIC3622I: There is no indoubt batch to commit for the WebSphere MQ link sender with channel name {1} defined on WebSphere MQ link {0}.
Explanation An attempt was made to commit an indoubt batch of messages when there was no indoubt batch of messages. Action No action is required.
CWSIC3623I: There is no indoubt batch to rollback for the WebSphere MQ link sender with channel name {1} defined on WebSphere MQ link {0}.
Explanation An attempt was made to rollback an indoubt batch of messages when there was no indoubt batch of messages. Action No action is required.
CWSIC3630I: The message with id {0} could not be moved or deleted as it is currently part of an indoubt batch.
Explanation An attempt was made to move or delete a message with the stated id but it could not be completed as it was part of an indoubt batch. Action Consider rolling the batch back if the message needs to be moved or deleted. Otherwise no action is necessary unless the batch remains in the indoubt state for an extended period of time.
CWSIC3631I: The message with id {0} could not be moved or deleted as WebSphere MQ link {1} has a WebSphere MQ link sender {2} which is not in the stopped state.
Explanation An attempt was made to move or delete a message with the stated id but it could not be completed as the stated WebSphere MQ link sender is not in the stopped state. Action Consider stopping the stated WebSphere MQ link sender if the message needs to be moved or deleted. Otherwise no action is necessary.
CWSIC3632I: The messages with the following ids {0} could not be moved or deleted as they are currently part of an indoubt batch.
Explanation An attempt was made to move or delete messages but the stated messages could not be moved or deleted as they were part of an indoubt batch. Action Consider rolling the batch back if the messages need to be moved or deleted. Otherwise no action is necessary unless the batch remains in the indoubt state for an extended period of time.
CWSIC3633I: Messages could not be moved or deleted as WebSphere MQ link {0} has a WebSphere MQ link sender {1} which is not in the stopped state.
Explanation An attempt was made to move or delete messages but it couldn't be completed as the stated WebSphere MQ link sender is not in the stopped state. Action Consider stopping the stated WebSphere MQ link sender if the messages need to be moved or deleted. Otherwise no action is necessary.
CWSIC3640E: The WebSphere MQ link sender channel {0}, defined in WebSphere MQ link {1}, is not stopped.
Explanation An attempt was made to test a foreign bus connection when the stated WebSphere MQ link sender channel was running. Action Stop the stated WebSphere MQ link sender channel in state STOPPED, then repeat the test connection request.
CWSIC3641E: A WebSphere MQ link sender channel is not configured in WebSphere MQ link {0}.
Explanation An attempt was made to test a foreign bus connection but a WebSphere MQ link sender channel has not been configured for the stated WebSphere MQ link. Action Configure a WebSphere MQ link sender channel on the stated MQ link, then repeat the test connection request.
CWSIC3642E: The WebSphere MQ link sender channel {0}, defined in WebSphere MQ link {1}, was unable to create and send a data flow to remote host {2}.
Explanation An attempt was made to test a foreign bus connection but the stated WebSphere MQ link sender channel was unable to create a data flow for subsequent transfer to the partner receiver channel on the stated remote host. Action An internal error has occurred. For further information on resolving this error, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3643E: A connection to remote host {0}, on port number {1}, cannot be established.
Explanation An attempt was made to test a foreign bus connection but a connection could currently not be established to the stated remote host on the stated port. It is possible that there is some sort of transitory resource constraint. Action Repeat the action at a later point in time. For further information on resolving this error, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3644E: The ping channel data {0} received from the partner receiver channel is not the same as the original data {1} that was sent by WebSphere MQ link sender channel {2}, defined in WebSphere MQ link {3}.
Explanation The ping channel function is used when testing a foreign bus connection. This function involves sending data to the partner receiver channel. The partner receiver channel is expected to return the data that it receives but it has not done so. Action Try repeating the test connection request. For further information on resolving this error, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3645E: No response was received from remote host {0} listening on port {1}.
Explanation An attempt was made to test a foreign bus connection but the partner receiver channel did not respond within the inbuilt timeout period. It is possible that the remote host is unavailable, or cannot be reached due to network delays. Action Determine why the remote host is unavailable. Repeat the action when the remote host is available and listening on the stated port.
CWSIC3646E: The partner receiver channel has requested the WebSphere MQ link sender channel {0}, defined in WebSphere MQ link {1}, to close.
Explanation An attempt was made to test a foreign bus connection but the partner receiver channel has requested closure of the channel. Action Determine why the partner receiver channel has requested closure, resolve the issue then repeat the test connection request.
CWSIC3647E: The WebSphere MQ link sender channel {0}, defined in WebSphere MQ link {1}, has encountered a communications error.
Explanation An attempt was made to test a foreign bus connection but the WebSphere MQ link sender channel encountered an unrecoverable communications error. Action It is possible that this is a transient error. Try repeating the test connection request. For further information on resolving this error, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3648E: The partner receiver channel failed to return the original ping channel data that was sent by WebSphere MQ link sender channel {0}, defined in WebSphere MQ link {1}.
Explanation The ping channel function is used when testing a foreign bus connection. This function involves sending data to the partner. The partner is expected to return the data that it receives but it has not returned any data. Action Try repeating the test connection request. For further information on resolving this error, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3649E: A problem was encountered while attempting to convert the ping channel data into encoding {0}.
Explanation The ping channel function is used when testing a foreign bus connection. This function involves sending ping channel data to the partner which, in turn, returns the data. A problem has been encountered while converting the ping channel data into the stated encoding. Action Ensure that the Java Virtual Machine (JVM) you are running with supports the specified encoding. For further information on resolving this error, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.
CWSIC3650I: WebSphere MQ link {0} has been disabled because all WebSphere MQ functionality on this server has been disabled.
Explanation All WebSphere MQ functionality has been disabled on this server as a result of the 'disable WebSphere MQ functionality' check box being selected on a WebSphere MQ messaging provider panel at an appropriate scope. Alternatively the manageWMQ administrative command may have been used to disable WebSphere MQ functionality. As a result of this all WebSphere MQ link functionality has been disabled. Action None unless WebSphere MQ link functionality is required, in which case clear the 'disable WebSphere MQ functionality' check box on the relevant WebSphere MQ messaging provider panel or make use of the manageWMQ administrative command.
CWSIC3651I: It is not possible to test the connection between WebSphere MQ link {0} and its partner queue manager as all WebSphere MQ functionality has been disabled on the server on which this WebSphere MQ link is currently running.
Explanation All WebSphere MQ functionality has been disabled on the server running the named WebSphere MQ link as a result of the 'disable WebSphere MQ functionality' check box being selected on a WebSphere MQ messaging provider panel at an appropriate scope. Alternatively the manageWMQ administrative command may have been used to disable WebSphere MQ functionality. As a result of this all WebSphere MQ link functionality has been disabled. Action None unless WebSphere MQ link functionality is required, in which case clear the 'disable WebSphere MQ functionality' check box on the relevant WebSphere MQ messaging provider panel or make use of the manageWMQ administrative command.
CWSIC3700I: An internal error occurred. Unknown MQClientLink parameter {0} with value {1}.
Explanation During initialization of an MQClientLink object, an unknown parameter was encountered. The unknown parameter will be ignored and initialization will continue. Action More info at:
CWSIC3701E: A WebSphere MQ connection attempt from host {0} on transport chain {1} using a user identifier of {2} failed to be authenticated.
Explanation The WebSphere MQ connection described in the message has failed a security check. Action Examine the error logs to determine why the specified WebSphere MQ process cannot connect using the user identifier.
CWSIC3702E: A WebSphere MQ connection attempt from host {0} on transport chain {1} failed because the queue manager it referenced, {2}, does not correspond to an active MQClientLink defined to this application server.
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 Examine the error logs to determine why the MQClientLink is not available.
CWSIC3703E: A WebSphere MQ connection attempt from host {0} on transport chain {1} failed because the channel it referenced, {2}, does not correspond to the channel name in the MQClientLink named {3}.
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 Examine the error logs to determine what the correct channel name should be.
CWSIC3704I: A WebSphere MQ client application has connected from host {0} on transport chain {1}.
Explanation A WebSphere MQ client application has connected to this application server from the specified host using the specified transport chain. Action No action is required.
CWSIC3705I: A WebSphere MQ client, previously connected from host {0} on transport chain {1}, has disconnected.
Explanation A WebSphere MQ client has disconnected from this application server. Action No action is required.
CWSIC3706E: An attempt to locate the Messaging Engine for a given connection has failed. The Messaging Engine being located was {0}.
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 Examine the error logs to determine why the Messaging engine is no longer available.
CWSIC3707E: A connection to Messaging Engine {0} has been dropped.
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, alternatively, examine the error logs to determine why the connection could have been dropped.
CWSIC3708E: A connection to Messaging Engine {0} has been lost.
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, alternatively, examine the error logs to determine why the connection could have been lost.
CWSIC3709E: MQClientLink {0} has encountered an internal error.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC3710E: A WebSphere MQ connection attempt from host {0} on transport chain {1} failed because there is no suitable MQClientLink object defined for the queue manager being connected to.
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 Determine why an MQClientLink object does not exist for the specified queue manager. Define one if required.
CWSIC3711E: A WebSphere MQ connection attempt from host {0} on transport chain {1} failed because the channel it referenced, {2}, does not correspond to an active MQClienLink defined to this application server.
Explanation The WebSphere MQ connection described by the message failed because it referenced a channel name which did not correspond to an active MQClientLink. Action Determine why an MQClientLink object does not exist for the specified channel. Define one if required.
CWSIC3712E: A WebSphere MQ client, previously connected from host {0} on transport chain {1}, has been disconnected because of exception {2}.
Explanation A connection from a WebSphere MQ client has been lost. This may be due to a communications failure. It is possible that the WebSphere MQ client application has terminated. Action Restart the WebSphere MQ client if required, otherwise ask the system administrator to determine why the connection could have been dropped.
CWSIC3713I: WebSphere MQ client link {0} has been disabled because all WebSphere MQ functionality on this server has been disabled.
Explanation All WebSphere MQ functionality has been disabled on this server as a result of the 'disable WebSphere MQ functionality' check box being selected on a WebSphere MQ messaging provider panel at an appropriate scope. Alternatively the manageWMQ administrative command may have been used to disable WebSphere MQ functionality. As a result of this all WebSphere MQ client link functionality has been disabled. Action None unless WebSphere MQ client link functionality is required, in which case clear the 'disable WebSphere MQ functionality' check box on the relevant WebSphere MQ messaging provider panel or make use of the manageWMQ administrative command.
CWSIC8002E: An internal error occurred. An unknown or unexpected exception was thrown by the core API: exception {0}.
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 More info at:
CWSIC8003E: An internal error occurred. Calling method {0} on the client is prohibited.
Explanation A method call was made on the client that should only be called on the server. Action More info at:
CWSIC8004E: An internal error occurred. An incorrect value was supplied for timeout property. The value supplied was {0}.
Explanation An attempt was made to set a property but the value supplied was incorrect for the property. Action More info at:
CWSIC8005E: It is not possible to encode a string using the encoding {0} due to exception: {1}.
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.
CWSIC8006E: An attempt was made to transmit a string, but the string supplied was too long (length = {0}, maximum length = {1}).
Explanation The string cannot be sent across the network as it exceeds the length of strings which may be sent using the messaging protocols. Action Correct the string to reduce its length and repeat the operation.
CWSIC8007E: An exception was caught from the remote server with Probe Id {1}. Exception: {0}.
Explanation The remote server generated an exception that caused a FFDC. Action Examine the exception and the corresponding FFDC file on the server to determine the problem and retry your operation.
CWSIC8008E: An internal error occurred. An incorrect value was supplied for connection type property. The value supplied was {0}.
Explanation An attempt was made to set a property but the value supplied was incorrect for the property. Action More info at:
CWSIC8009E: An internal error occurred. An incorrect value was supplied as a handshake parameter. The value supplied was {0}.
Explanation Handshaking information was received that was not understood. Action More info at:
CWSIC8010E: An internal error occurred. The messaging engines were not able to agree upon initial communication parameters.
Explanation The messaging engine handshake has failed due to an incorrect property. Action More info at:
CWSIC8011E: An internal error occurred. An incorrect value was supplied to the messaging engine in the segment field. The value was {0}.
Explanation An attempt was made to set a property but the value supplied was incorrect for the property. Action More info at:
CWSIC8012E: An internal error occurred. The client and messaging engine were not able to agree upon initial communication paramters.
Explanation The client handshake has failed due to an incorrect property. Action More info at:
CWSIC8013E: An internal error occurred. An incorrect value was supplied for consumer flags. The value was {0}.
Explanation An attempt was made to set a property but the value supplied was incorrect for the property. Action More info at:
CWSIC8014E: An internal error occurred. An incorrect value was supplied for consumer flags. The value was {0}.
Explanation An attempt was made to set a property but the value supplied was incorrect for the property. Action More info at:
CWSIC8015I: Client {0} connection started from {1}.
Explanation A client connection with the specified user identifier was established from the specified network address. Action No action is required.
CWSIC8016I: Client {0} disconnected.
Explanation A client connection with the specified user identifier has ended. Action No action is required.
CWSIC8017E: An internal error occurred. An incorrect value was supplied for browser flags. The value was {0}.
Explanation An attempt was made to set a property but the value supplied was incorrect for the property. Action More info at:
CWSIC8018E: An internal error occurred. An incorrect value was supplied for producer flags. The value was {0}.
Explanation An attempt was made to set a property but the value supplied was incorrect for the property. Action More info at:
CWSIC8019E: An internal error occurred. The destination listener id {0} received by the client can not be located.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC8020E: An internal error occurred. The ProxyQueueConversationGroup is null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC8021E: An internal error occurred. The proxyQueue is not an instance of AsynchConsumerProxyQueue but is an instance of {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC8022E: An internal error occurred. The asynchConsumerCallback is not an instance of StoppableAsynchConsumerCallback but is an instance of {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIC8023E: It is not possible to encode a string using the encoding {0} due to exception: {1}.
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.
CWSIC9999E: {0}
Explanation If the message does not give sufficient information, check previous messages for further help. Action For further information on resolving this error, see the problem determination information on the Application Server Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support.