T TRM messages

CWSIT0000E: An internal error occurred. An object of class {0} cannot be created because of exception: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0001E: An internal error occurred. A null {0} was used to created a {1} instance.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0002E: An internal error occurred. A null {0} was passed on a {1} method call.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0003E: No {0} property was found in the connection properties.
Explanation: A required property was not found in the connection properties when creating a client connection.
User Response: Ensure that the required property is correctly specified when creating a connection.

CWSIT0004E: An internal error occurred. An object of class ClientConnectionFactory cannot be created.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0005E: An internal error occurred. An object of class ClientConnection cannot be created.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0006E: It is not possible to contact a messaging engine in bus {0}.
Explanation: The client cannot establish contact with a bootstrap server. This situation may be due to network problems or it may be that none of the required bootstrap servers are currently available.
User Response: Ensure that the network is working correctly and that the required bootstrap servers are available.

CWSIT0007W: It is not possible to contact the bootstrap server at {0}.
Explanation: The client cannot establish contact with the specified bootstrap server. This situation may be due to network problems or it may be that the required bootstrap server is currently unavailable.
User Response: Ensure that the network is working correctly and that the required bootstrap server is available.

CWSIT0008E: It is not possible to contact the messaging engine {0} in bus {1} to which the client was redirected.
Explanation: The client cannot establish contact with the messaging engine to which it was redirected by the bootstrap server. This situation may be due to network problems or it may be that the required messaging engine is currently unavailable.
User Response: Ensure that the network is working correctly and that the required messaging engine is available.

CWSIT0009W: A client request failed in the application server with endpoint {0} in bus {1} with reason: {2}.
Explanation: A client bootstrap request failed because of a problem in an application server. The reason for the failure in the application server is returned. The client bootstrap process will continue with the next provider endpoint in the provider endpoints list.
User Response: Ask your system administrator to investigate the logs for the application server to help determine the reason for the failure.

CWSIT0010E: A client request for messaging engine {0} in bus {1} failed with reason: {2}.
Explanation: A client failed to attach to a bus because of a failure in a server. The reason for the failure in the server is returned.
User Response: Ask your system administrator to investigate the logs for the messaging engine to help determine the reason for the problem.

CWSIT0011E: It is not possible to attach to messaging engine {0} in bus {1}.
Explanation: The client cannot establish contact with the named messaging engine. This situation may be due to network problems or it may be that the required messaging engine is currently unavailable.
User Response: Ensure that the network is working correctly and that the required messaging engine is available.

CWSIT0012E: An internal error occurred. A null {0} was used to created a {1} instance.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0013E: An internal error occurred. A null {0} was used to created a {1} instance.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0014E: A messaging engine to messaging engine request failed in messaging engine {0} in bus {1}, endpoint {2}, with reason: {3}.
Explanation: A messaging engine to messaging engine request failed because of a failure in the remote messaging engine.
User Response: Ask your system administrator to investigate the logs for the remote messaging engine to help determine the reason for the problem.

CWSIT0015W: It is not possible to connect to messaging engine {0} in bus {1}.
Explanation: The messaging engine cannot establish contact with another messaging engine. This situation may be due to network problems or it may be that the required messaging engine is currently unavailable.
User Response: Ensure that the network is working correctly and that required messaging engine is available.

CWSIT0016E: The user ID {0} failed authentication in bus {1}
Explanation: The user ID used to create a client connection with a messaging engine failed to be authenticated by the remote messaging engine. The authentication failure was probably due to an incorrect user ID or password value.
User Response: Ensure that both the user ID and password values are correct.

CWSIT0017W: It is not possible to create an intra-bus connection to messaging engine {0} in bus {1} on host {2} port {3} using protocol {4}.
Explanation: The messaging engine cannot establish contact with another messaging engine. This situation may be due to network problems or it may be that the required messaging engine is currently unavailable.
User Response: Ensure that the network is working correctly and that required messaging engine is available.

CWSIT0018W: It is not possible to create the inter-bus connection {0} to messaging engine {1} in bus {2}, on host {3} port {4} using protocol {5}.
Explanation: The messaging engine cannot establish contact with another messaging engine. This situation may be due to network problems or it may be that the required messaging engine is currently unavailable.
User Response: Ensure that the network is working correctly and that required messaging engine is available.

CWSIT0019E: No suitable messaging engine is available in bus {0}
Explanation: A client could not be attached to the bus because no suitable messaging engine is available at this time that meets with the attachment criteria specified by the connection properies.
User Response: Repeat the operation. If the problem persists then ask your system administrator to check that a suitable messaging engine is available. Alternatively relax the attachment criteria specified by the connection properties and repeat the operation.

CWSIT0020E: An unexpected exception occurred in messaging engine {0} in bus {1} while creating a connection, exception: {2}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0021E: The required messaging engine {0} in bus {1} was not found in this process
Explanation: A client could not be attached to the bus because the required messaging engine could not be found in the process to which the client attached.
User Response: Repeat the operation. If the problem persists then ask your system administrator to resolve the problem.

CWSIT0022E: The user ID {0} failed authentication in bus {1}.
Explanation: The user ID used to create an intra-bus messaging engine connection failed to be authenticated by the remote messaging engine. The authentication failure was probably due to an incorrect user ID or password value.
User Response: Ensure that both the user ID and password values are correct.

CWSIT0023E: Topology rules do not permit connections between messaging engines with the same name
Explanation: A messaging engine with the same name attempted to connect to this messaging engine. Two messaging engines with the same name are not permitted within the same bus.
User Response: Check the bus topology and messaging engine names.

CWSIT0024E: An internal error occurred. An object of class {0} cannot be created because of exception: {1}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0025E: Messaging engine {0} in subnet {1} in bus {2} attempted to create an intra-bus connection to messaging engine {3}
Explanation: A messaging engine in the same subnet attempted to create an intra-bus connection to this messaging engine. Topology rules do not permit intra-bus connections between messaging engines in the same subnet.
User Response: Check the bus topology.

CWSIT0026E: Messaging engine {0} in bus {1} attempted to create an inter-bus connection to messaging engine {2}
Explanation: A messaging engine in the same bus attempted to create an inter-bus connection to this messaging engine. Topology rules do not permit inter-bus connections between messaging engines in the same bus.
User Response: Check the bus topology.

CWSIT0027E: A messaging engine with UUID {0} was not found in this process
Explanation: A client could not be attached to the requested messaging engine because the required messaging engine could not be found in the process to which the client attached.
User Response: Repeat the operation. If the problem persists then ask your system administrator to resolve the problem.

CWSIT0028I: The connection for messaging engine {0} in bus {1} to messaging engine {2} started.
Explanation: A messaging engine to messaging engine connection has been started.
User Response: No action required.

CWSIT0029I: The connection for messaging engine {0} in bus {1} to messaging engine {2} stopped.
Explanation: A messaging engine to messaging engine connection has been stopped.
User Response: No action required.

CWSIT0030I: The intra-bus connection for messaging engine {0} in subnet {1} in bus {2} to messaging engine {3} in subnet {4} started.
Explanation: A messaging engine to messaging engine intra-bus connection has been started.
User Response: No action required.

CWSIT0031I: The intra-bus connection for messaging engine {0} in subnet {1} in bus {2} to messaging engine {3} in subnet {4} stopped.
Explanation: A messaging engine to messaging engine intra-bus connection has been stopped.
User Response: No action required.

CWSIT0032I: The inter-bus connection {0} from messaging engine {1} in bus {2} to messaging engine {3} in bus {4} started.
Explanation: A messaging engine to messaging engine inter-bus connection has been started.
User Response: No action required.

CWSIT0033I: The inter-bus connection {0} from messaging engine {1} in bus {2} to messaging engine {3} in bus {4} stopped.
Explanation: A messaging engine to messaging engine inter-bus connection has been stopped.
User Response: No action required.

CWSIT0034E: A messaging engine to messaging engine request failed in messaging engine {0} in bus {1} with reason: {2}.
Explanation: A messaging engine to messaging engine request failed because of a failure in the remote messaging engine. The reason for the failure in the remote messaging engine is returned.
User Response: Ask your system administrator to investigate the logs for the remote messaging engine to help determine the reason for the problem.

CWSIT0035E: The user ID {0} failed authentication in bus {1}
Explanation: The user ID used to create a intra-bus messaging engine connection failed to be authenticated by the remote messaging engine. The authentication failure was probably due to an incorrect user ID or password value.
User Response: Ensure that both the user ID and password values are correct.

CWSIT0036E: An internal error occurred. There is a client protocol error while communicating with messaging engine {0} in bus {1}, the received message type is {2} but the expected message type is {3}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0037E: An internal error occurred. There is a client protocol error while communicating with the messaging engine with UUID {0}, the received message type is {1} but the expected message type is {2}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0038E: An internal error occurred. There is a client bootstrap protocol error while communicating with a messaging engine in bus {0}, the received message type is {1} but the expected message type is {2}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0039E: An internal error occurred. There is a connection protocol error while communicating with messaging engine {0} in bus {1}, the received message type is {2} but the expected message type is {3}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0040E: An internal error occurred. There is a intra-bus connection protocol error while communicating with messaging engine {0} in bus {1}, the received message type is {2} but the expected message type is {3}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0041E: An internal error occurred. There is an inter-bus connection protocol error while communicating with messaging engine {0} in bus {1}, the received message type is {2} but the expected message type is {3}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0042E: An internal error occurred. There is a connect protocol error while communicating with messaging engine {0} in bus {1}, the received message type is {2} but the expected message type is {3}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0043E: An internal error occurred. There is a intra-bus connection protocol error while communicating with messaging engine {0} in bus {1}, the received message type is {2} but the expected message type is {3}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0044E: An internal error occurred. An object of class MEConnectionFactory cannot be created.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0045E: An internal error occurred. An object of class MEConnectionFactory cannot be created.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0046E: An internal error occurred. An object of class MEConnectionFactory cannot be created.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0047E: An internal error occurred. An object of class MEConnection cannot be created.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0048E: An internal error occurred. An object of class MEConnection cannot be created.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0049E: An internal error occurred. An object of class MEConnection cannot be created.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0050E: An internal error occurred. A reference to the Topology Routing and Management component cannot be obtained from the Administration component
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0051E: An internal error occurred. A reference to the Topology Routing and Management component cannot be obtained from the Administration component
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0052E: An internal error occurred. A reference to the Topology Routing and Management component cannot be obtained from the Administration component
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0053E: An internal error occurred. The expected byte value {0} was not found, instead a byte value of {1} was found.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0054E: An internal error occurred. The expected byte value {0} was not found, instead a byte value of {1} was found.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0055E: An incorrect value {0} was passed for the connection property {1}, valid values are: {2}.
Explanation: The application provided a connection property value that is not correct, the connection is not created.
User Response: Correct the application to use a valid value for the connection property.

CWSIT0056E: The user ID {0} failed authentication in bus {1}
Explanation: The user ID used to create a inter-bus messaging engine connection failed to be authenticated by the remote messaging engine. The authentication failure was probably due to an incorrect user ID or password value.
User Response: Ensure that both the user ID and password values are correct.

CWSIT0057E: The inter-bus connection {0} failed in the remote messaging engine on host {1} with reason: {2}.
Explanation: An inter-bus messaging engine to messaging engine request failed because of a failure in the remote messaging engine.
User Response: Ask your system administrator to investigate the logs for the remote messaging engine to help determine the reason for the problem.

CWSIT0058E: It is not possible to complete the inter-bus connection {0} because the remote bus {2} returned an unexpected messaging engine name {3}, the expected messaging engine name was {1}.
Explanation: Inter-bus connections require that the name of the messaging engine in the remote bus match the messaging engine name configured for the inter-bus connection.
User Response: Check the inter-bus connection configuration to ensure that both buses have the correct messaging engine name configured.

CWSIT0059E: It is not possible to establish the inter-bus connection {0} to messaging engine {1} in bus {2}.
Explanation: Contact can not be made with the named messaging engine. This situation may be due to network problems or it may be that the required messaging engine is currently unavailable.
User Response: Ensure that the network is working correctly and that the required messaging engine is available.

CWSIT0060E: The user ID {0} is not authorized to create an intra-bus messaging engine connection in bus {1}
Explanation: The user ID used to create an intra-bus messaging engine connection was not the same user ID as the remote messaging engine has been authorized to allow to create intra-bus messaging engine connections.
User Response: Ensure that both messaging engines have the same user ID configured for intra-bus messaging engine connections.

CWSIT0061E: An internal error occurred. There is an inter-bus connection protocol error while communicating with messaging engine {0} in bus {1}, the received message type is {2} but the expected message type is {3}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0062E: An internal error occurred. There is an inter-bus connection protocol error while communicating with messaging engine {0} in bus {1}, the received message type is {2} but the expected message type is {3}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0063E: The required messaging engine {0} in bus {1} was not found in this process
Explanation: The messaging engine could not communicate with a neighboring messaging engine because the neighbor messaging engine could not be found in the process to which this messaging engine connected.
User Response: Repeat the operation. Ensure that the required messaging engine is available at the correct location.

CWSIT0064E: The required messaging engine {0} in bus {1} was not found in this process
Explanation: The messaging engine could not communicate with a neighboring messaging engine because the neighbor messaging engine could not be found in the process to which this messaging engine connected.
User Response: Repeat the operation. Ensure that the required messaging engine is available at the correct location.

CWSIT0065E: The required messaging engine {0} in bus {1} was not found in this process
Explanation: The messaging engine could not communicate with a neighboring messaging engine because the neighbor messaging engine could not be found in the process to which this messaging engine connected.
User Response: Repeat the operation. Ensure that the required messaging engine is available at the correct location.

CWSIT0066E: It is not possible to complete the inter-bus connection {0} because the messaging engine in the requesting bus {1} is attempting to connect to a messaging engine in the same bus
Explanation: A messaging engine attempted to establish an inter-bus connection to a messaging engine in the same bus. Inter-bus connections between messaging engines in the same bus are not permitted.
User Response: Check the inter-bus connection configuration to ensure that the bootstrap endpoints correctly address a remote bus.

CWSIT0067E: Inter-bus connection {0} in bus {1} is not available
Explanation: An inter-bus connection request was received from another bus but there is no messaging engine available to accept the request in the target bus.
User Response: Ensure that the messaging engine configured to handle the inter-bus connection is available.

CWSIT0068E: An inter-bus connection request was received for {0} from bus {1} messaging engine {2} but no matching configuration definition could be found.
Explanation: An inter-bus connection request was received from another bus but no configuration definition could be found which matched this request, the request was rejected.
User Response: Ensure that the inter-bus connection configurations in both buses are correct.

CWSIT0069E: No matching configuration was found for the inter-bus connection {0} in bus {1}
Explanation: An inter-bus connection request was rejected by another bus because no configuration definition could be found which matched this request.
User Response: Ensure that the inter-bus connection configurations in both buses are correct.

CWSIT0070E: An inter-bus connection request was received for {0} from bus {1} messaging engine {2} but the configuration definition expects messaging engine {3}.
Explanation: An inter-bus connection request was received from a messaging engine in another bus which is not the messaging engine named in the configuration definition in this bus, the request was rejected.
User Response: Ensure that the inter-bus connection configurations in both buses are correct.

CWSIT0071E: The inter-bus connection request for link {0} was rejected by bus {1} because the requesting messaging engine {2} did not match the expected messaging engine {3}
Explanation: The remote bus detected an inconsistency in the messaging engine named in the inter-bus connection request made by this bus and its own inter-bus configuration definition.
User Response: Ensure that the inter-bus connection configurations in both buses are correct.

CWSIT0072W: Unable to obtain authentication data from the intra-bus messaging engine authentication alias {0}.
Explanation: If the authentication alias does not exist or is incorrectly configured it will not be possible to obtain authentication data from it. Default empty string values will be assumed for authentication data required for intra-bus messaging engine connections. If security is enabled then this problem will prevent messaging engines connecting.
User Response: Ensure that the intra-bus messaging engine authentication alias is correctly configured.

CWSIT0073W: No intra-bus messaging engine authentication alias is configured.
Explanation: When no intra-bus messaging engine authentication alias is configured no authentication check will be performed for intra-bus messaging engine connections. To authenticate intra-bus messaging engine connections configure an intra-bus messaging engine authentication alias.
User Response: Configure the intra-bus messaging engine authentication alias.

CWSIT0074E: An internal error occurred. The link UUID {0} is already defined.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0075E: An internal error occurred. The link UUID {0} is already defined.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0076E: An internal error occurred. The link UUID {0} has not been defined.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0077E: An internal error occurred. The link UUID {0} has not been defined.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0078E: An internal error occurred. The link UUID {0} can not be registered because the link is not started.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0079E: An internal error occurred. The link UUID {0} can not be registered because the link is not active.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0080W: Unable to establish the inter-bus link {0} from bus {1} to bus {2} because the link in bus {3} is not started.
Explanation: The inter-bus link is currently started in one bus but not started in the other bus, the link must be started in both buses before connection will be possible.
User Response: Stop the inter-bus link in the originating bus or start the inter-bus link in the receiving bus.

CWSIT0081E: An internal error occurred. Bridge neighbor with UUID {0} not found in the neighborhood.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0082E: An internal error occurred. Neighbor with UUID {0} not found in the neighborhood.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0083E: An internal error occurred. No cluster member found when one was expected.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0084E: An internal error occurred. WLM state is inconsistent, reason: {0}.
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSIT0085E: The user ID {0} is not authorized to create the inter-bus connection {1} between bus {2} and bus {3}
Explanation: The user ID used to create an inter-bus connection was not the same user ID as the remote messaging engine has been authorized to allow to create inter-bus connections.
User Response: Ensure that both messaging engines have the same user ID configured for this inter-bus connection.

CWSIT0086E: Bus {0} not found
Explanation: The required bus is not configured in the server therefore it is not possible to use this server to connect to the required bus.
User Response: Ensure that the bus name is correct and use a server that has the required bus configured.

CWSIT0087E: An intra-bus connection request was received from messaging engine {1} but no matching configuration definition could be found.
Explanation: An intra-bus connection request was received from another messaging engine but no configuration definition could be found which matched this request, the request was rejected.
User Response: Ensure that the intra-bus connection configurations in both messaging engines are correct.

CWSIT0088E: There are currently no messaging engines running in bus {0}
Explanation: A client could not be attached to the bus because there are no messaging engines running in the bus at this time.
User Response: Repeat the operation. If the problem persists then ask your system administrator to start a messaging engine in the required bus.

CWSIT9999E: {0}
Explanation: If the message does not give sufficient information, check any previous messages for further information.
User Response: If you are not able to resolve the problem ask your system administrator to help resolve the problem.