CWSIT

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.

Action

If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J .

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.

Action

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.

Action

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.

Action

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.

Action

CWSIT0005E: An internal error occurred. An object of class ClientConnection cannot be created.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSIT0006E: It was not possible to contact any of the specified bootstrap servers. Please see the linked exception for further details. Bootstrap connections were attempted to: {0}

Explanation

The client cannot connect to the bus. This situation may be due to configuration problems, network problems or it may be that none of the required bootstrap servers are currently available.

Action

Ensure that the network is working correctly and that the required bootstrap servers are available. See the Information Center for details on configuring a connection to a bootstrap server.

CWSIT0007W: It is not possible to contact the bootstrap server at {0} because of exception: {1}.

Explanation

The client cannot establish contact with the specified bootstrap server. This situation may be due to configuration problems, network problems or it may be that the required bootstrap server is currently unavailable. The client bootstrap process will continue with the next provider endpoint in the provider endpoints list.

Action

Ensure that the network is working correctly and the required bootstrap server is available. The bootstrap server is specified by the Provider Endpoint property of the JMS connection factory. The endpoint address has the form host_name:port_number:chain_name (for example, localhost:7276:BootstrapBasicMessaging). The connection factory must specify the Provider Endpoint property if a non-default bootstrap server is being used.

CWSIT0008E: A successful connection was made to the bootstrap server at {0} but the server returned an error condition: {1}

Explanation

The client connected to a bus but experienced a problem using the service. This situation may be due to network problems or it may be that the required service is currently unavailable.

Action

Ensure that the network is working correctly and that the required service is available. See the Information Center for details on configuring a connection to a bootstrap server.

CWSIT0009W: A client connect to bus {1} failed in the bootstrap server with endpoint {0} with reason: {2}.

Explanation

A client bootstrap request failed because of a problem in a bootstrap server. The reason for the failure in the bootstrap server is returned. The client bootstrap process will continue with the next provider endpoint in the provider endpoints list.

Action

Investigate and resolve the failure described in the error message, then retry the operation.

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.

Action

Investigate and resolve the failure described in the error message, then retry the operation.

CWSIT0011E: It is not possible to attach to messaging engine {0} in bus {1}. The connection has been lost.

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.

Action

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.

Action

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.

Action

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.

Action

Investigate and resolve the failure described in the error message, then retry the operation.

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 might be due to network problems or it might be that the required messaging engine is currently unavailable.

Action

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 that was used to create a client connection with a messaging engine was unable to be authenticated by the remote messaging engine. The authentication failure was probably due to an incorrect user ID or password value.

Action

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 transport chain {4}.

Explanation

Action

Ensure that the network is working correctly and that required messaging engine is available.

CWSIT0018W: It is not possible to create the service integration bus link {0} to messaging engine {1} in bus {2}, on host {3} port {4} using transport chain {5}.

Explanation

Action

Ensure that the network is working correctly and that required messaging engine is available.

CWSIT0019E: No suitable messaging engine is available on bus {0} that matched the specified connection properties {1}. Reason for failure: {2}

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 properties.

Action

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.

Action

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.

Action

This error is usually caused by a transient condition such as the failure of a server during a client redirection. Retrying the operation should resolve the error.

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.

Action

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.

Action

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.

Action

CWSIT0026E: Messaging engine {0} in bus {1} attempted to create a service integration bus link to messaging engine {2}

Explanation

A messaging engine in the same bus attempted to create a service integration bus link to this messaging engine. Topology rules do not permit service integration bus links between messaging engines in the same bus.

Action

Check the bus topology.

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.

Action

No action is 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.

Action

No action is 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.

Action

No action is 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.

Action

No action is required.

CWSIT0032I: The service integration bus link {0} from messaging engine {1} in bus {2} to messaging engine {3} in bus {4} started.

Explanation

A service integration bus link between two messaging engines has been started.

Action

No action is required.

CWSIT0033I: The service integration bus link {0} from messaging engine {1} in bus {2} to messaging engine {3} in bus {4} stopped.

Explanation

A service integration bus link between two messaging engines has been stopped.

Action

No action is 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.

Action

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

Action

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.

Action

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.

Action

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.

Action

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.

Action

CWSIT0041E: An internal error occurred. There is a service integration bus link 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.

Action

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.

Action

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.

Action

CWSIT0044E: An internal error occurred. An object of class MEConnectionFactory cannot be created.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSIT0045E: An internal error occurred. An object of class MEConnectionFactory cannot be created.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSIT0046E: An internal error occurred. An object of class MEConnectionFactory cannot be created.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSIT0047E: An internal error occurred. An object of class MEConnection cannot be created.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSIT0048E: An internal error occurred. An object of class MEConnection cannot be created.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSIT0049E: An internal error occurred. An object of class MEConnection cannot be created.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

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.

Action

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.

Action

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 has not been created.

Action

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 service integration bus link failed to be authenticated by the remote messaging engine. The authentication failure was probably due to an incorrect user ID or password value.

Action

Ensure that both the user ID and password values are correct.

CWSIT0057E: The service integration bus link {0} failed in the remote messaging engine on host {1} with reason: {2}.

Explanation

A service integration bus link request failed because of a failure in the remote messaging engine.

Action

Investigate and resolve the failure described in the error message, then retry the operation.

CWSIT0058E: It is not possible to complete the service integration bus link {0} because the remote bus {2} returned an unexpected messaging engine name {3}, the expected messaging engine name was {1}.

Explanation

Service integration bus links require that the name of the messaging engine in the remote bus match the messaging engine name configured for the service integration bus link.

Action

Check the service integration bus link configuration to ensure that both buses have the correct messaging engine name configured.

CWSIT0059E: It is not possible to establish the service integration bus link {0} to messaging engine {1} in bus {2}.

Explanation

Contact cannot be made with the named messaging engine. This situation might be due to network problems or it might be that the required messaging engine is currently unavailable.

Action

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 is not the same user ID as the remote messaging engine has been authorized to allow to create intra-bus messaging engine connections.

Action

Ensure that both messaging engines have the same user ID configured for intra-bus messaging engine connections.

CWSIT0061E: An internal error occurred. There is a service integration bus link 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.

Action

CWSIT0062E: An internal error occurred. There is a service integration bus link 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.

Action

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 neighboring messaging engine could not be found in the process to which this messaging engine connected.

Action

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 neighboring messaging engine could not be found in the process to which this messaging engine connected.

Action

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 neighboring messaging engine could not be found in the process to which this messaging engine connected.

Action

Repeat the operation. Ensure that the required messaging engine is available at the correct location.

CWSIT0066E: It is not possible to complete the service integration bus link {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 a service integration bus link to a messaging engine in the same bus. Service integration bus links between messaging engines in the same bus are not permitted.

Action

Check the service integration bus link configuration to ensure that the bootstrap endpoints correctly address a remote bus.

CWSIT0067E: Service integration bus link {0} in bus {1} is not available

Explanation

A service integration bus link request was received from another bus but there is no messaging engine available to accept the request in the target bus.

Action

Ensure that the messaging engine configured to handle the service integration bus link is available.

CWSIT0068E: A service integration bus link request was received for {0} from bus {1} messaging engine {2} but no matching configuration definition could be found.

Explanation

A service integration bus link request was received from another bus but no configuration definition could be found which matched this request, the request was rejected.

Action

Ensure that the service integration bus link configurations in both buses are correct.

CWSIT0069E: No matching configuration was found for the service integration bus link connection {0} in bus {1}

Explanation

A service integration bus link request was rejected by another bus because no configuration definition could be found which matched this request.

Action

Ensure that the service integration bus link configurations in both buses are correct.

CWSIT0070E: A service integration bus link request was received for {0} from bus {1} messaging engine {2} but the configuration definition expects messaging engine {3}.

Explanation

A service integration bus link 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.

Action

Ensure that the service integration bus link configurations in both buses are correct.

CWSIT0071E: The service integration bus link 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 service integration bus link request made by this bus and its own service integration bus link configuration definition.

Action

Ensure that the service integration bus link 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.

Action

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.

Action

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.

Action

CWSIT0075E: An internal error occurred. The link UUID {0} is already defined.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSIT0076E: An internal error occurred. The link UUID {0} has not been defined.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSIT0077E: An internal error occurred. The link UUID {0} has not been defined.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

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.

Action

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.

Action

CWSIT0080W: Unable to establish the service integration bus link {0} from bus {1} to bus {2} because the link in bus {3} is not started.

Explanation

The service integration 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.

Action

Stop the service integration bus link in the originating bus or start the 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.

Action

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.

Action

CWSIT0085E: The user ID {0} is not authorized to create the service integration bus link connection {1} between bus {2} and bus {3}

Explanation

The user ID used to create a service integration bus link connection was not the same user ID as the remote messaging engine has been authorized to allow to create service integration bus link connections.

Action

Ensure that both messaging engines have the same user ID configured for this service integration bus link.

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.

Action

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.

Action

Ensure that the intra-bus connection configurations in both messaging engines are correct.

CWSIT0088E: There are currently no messaging engines in bus {0} running. Additional failure information: {1}

Explanation

A client could not be attached to the bus because there are no messaging engines in the required bus running at this time.

Action

Repeat the operation. Start a messaging engine in the required bus.

CWSIT0089E: 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.

Action

Ensure that both the user ID and password values are correct.

CWSIT0090E: A bootstrap request was made to bus {0} using channel chain {1}. Use of this chain is not permitted by bus {0}.

Explanation

A client attempted to send a bootstrap request to connect to a bus, but the bus does not permit bootstrap requests using that channel.

Action

Reconfigure the client so that the bootstrap endpoint uses a permitted chain.

CWSIT0091W: A service integration bus link connection was successfully created to messaging engine {0} on bus {1} without specifying a service integration bus link authentication alias. It is recommended to configure an authentication alias for security reasons.

Explanation

When a service integration bus authentication alias is not configured on a service integration bus link it is possible to create a service integration bus link between a secure bus and an insecure bus without carrying out an authentication check.

Action

Configure the service integration bus link authentication alias if you want to enforce an authentication check.

CWSIT0092E: An attempt was made to connect to bus {0} using channel chain {1}. Use of this chain is not permitted by bus {0}.

Explanation

A client attempted to send a request to connect to a bus, but the bus does not permit connections using that channel chain.

Action

Reconfigure the client so that it connects using a permitted chain.

CWSIT0093E: Bus {0} attempted to create a service integration bus link to foreign bus {1} using bootstrap channel chain {2}. Use of this chain is not permitted by foreign bus {1}.

Explanation

A bus attempted to use a bootstrap transport chain that is not supported by the foreign bus.

Action

Reconfigure the bus so that the bootstrap endpoint uses a chain permitted by the foreign bus.

CWSIT0094E: The client was not authorized to connect to bus {0} using the bootstrap server with endpoint {1}. Reason: {2}.

Explanation

The user ID used to create a connection with the bus was not authorized to connect to the bus.

Action

Ensure that the user id has the bus connector role for the bus.

CWSIT0095E: Messaging engine {0} in bus {1} attempted to create a service integration bus link to messaging engine {2} in foreign bus {3} using inbound channel chain {4}. Use of this chain is not permitted by foreign bus {3}.

Explanation

A bus attempted to use an inbound transport chain that is not supported by the foreign bus.

Action

Reconfigure the bus so that it connects on a chain permitted by the foreign bus.

CWSIT0096E: Messaging engine {0} in bus {1} attempted to connect to messaging engine {2} using inbound channel chain {3}. Use of this chain is not permitted by bus {1}.

Explanation

The bus has been configured to use a transport channel chain that is not permitted for communication between messaging engines.

Action

Reconfigure the bus so that it specifies a permitted chain as the inter-engine transport chain.

CWSIT0097E: Messaging engine {0} in subnet {1} attempted to connect to messaging engine {2} in subnet {3} using inbound channel chain {4}. Use of this chain is not permitted by bus {5}.

Explanation

The bus attempted to use a transport channel chain that is not permitted.

Action

Reconfigure the bus so that it connects on a permitted transport channel chain.

CWSIT0098E: A client connect to bus {0} using the bootstrap server with endpoint {1} failed authentication with reason: {2}.

Explanation

Action

Ensure that both the user ID and password values are correct.

CWSIT0099E: The client successfully contacted the bootstrap server at endpoint {0} and was redirected to messaging engine {1} at the endpoint {2}. The attempt to contact this endpoint failed with the reason: {3}.

Explanation

A client failed to attach to a bus after a redirection because of a failure in a server. The reason for the failure in the server is returned.

Action

Investigate and resolve the failure described in the error message, then retry the operation.

CWSIT0100E: Expected to obtain a CFEndpoint from the Selection but none was present (internal error).

Explanation

The request to resolve a target messaging engine failed.

Action

CWSIT0101E: An invalid parameter was encountered.

Explanation

The request to resolve a target messaging engine failed.

Action

CWSIT0102E: A messaging engine selection {0} was found but had to be discarded because it does not satisfy the connection proximity constraint of {1} that was specified by the application.

Explanation

The request to resolve a target messaging engine failed.

Action

If you intended the connection to be made to the messaging engine shown in the error message, then you must relax the connection proximity in the connection factory or activation specification and retry the operation.

CWSIT0103E: No messaging engine was found that matched the following parameters: bus={0}, targetGroup={1}, targetType={2}, targetSignificance={3}, transportChain={4}, proximity={5}.

Explanation

The request to resolve a target messaging engine failed.

Action

Check the status of the messaging engine that you intended to connect to ensure that it is running. Alternatively, modify the connection properties to allow the selection of an active messaging engine.

CWSIT0104E: The client attempted to connect to the messaging engine {0} on bus {1} but the connection could not be created because the messaging engine is not started.

Explanation

The messaging engine exists but is not started.

Action

Start the messaging engine that you want to connect to, and retry the operation.

CWSIT0105E: The application did not specify a user ID when attempting to authenticate with the bus {0}

Explanation

Authentication with the remote messaging engine failed because the application did not specify a user ID.

Action

Ensure that both the user ID and password values are correct.

CWSIT0106I: Successfully created the service integration bus link {0} to messaging engine {1} in bus {2}, on host {3} port {4} using transport chain {5}.

Explanation

A bridge has been established with another messaging engine in a different bus.

Action

No action is required.

CWSIT0107W: The specified port {0}, in the endpoint, implied use of the transport chain {1}. This will result in the transmission of an unencrypted password between the client and the server. This is not recommended for security reasons.

Explanation

The default port is selected and the chain name was not specified in the provider endpoint. This results in a non secure transport chain, and it is recommended that you specify security on this connection.

Action

This warning can be prevented by manually specifying the required transport chain (either secure or insecure) or by omitting the password when creating a connection.

CWSIT0108E: The user ID {0} failed authorization in bus {1}

Explanation

The user ID used to create a client connection with a messaging engine failed to be authorized by the remote messaging engine. The authorization failure was probably due to an incorrect user ID or password value.

Action

Ensure that both the user ID and password values are correct.

CWSIT0109E: The application did not specify a user ID when attempting authorization with the bus {0}

Explanation

Authorization with the remote messaging engine failed because the application did not specify a user ID.

Action

Ensure that both the user ID and password values are correct.

CWSIT0110E: The security token provided by messaging engine {0} in bus {1} failed authentication.

Explanation

The security token used to create an intra-bus messaging engine connection failed to be authenticated.

Action

Check the error logs on the messaging engines involved in the connection attempt.

CWSIT0111E: The identity information provided in the security token did not match data in the connection request made by messaging engine {0} in bus {1}

Explanation

This may indicate that an unauthorized user is attempting to connect to the system.

Action

Check the error logs on the messaging engines involved in the connection attempt.

CWSIT0112E: The security token type of {0} provided by messaging engine {1} in bus {2} is not supported.

Explanation

Authentication of the remote messaging engine could not be carried out because the security token type is not supported.

Action

Check the error logs on the messaging engines involved in the connection attempt.

CWSIT0113E: The connection request from messaging engine {0} in bus {1} did not specify a security token type.

Explanation

This may indicate that an unauthorized user is attempting to connect to the system.

Action

Check the error logs on the messaging engines involved in the connection attempt.

CWSIT0115E: The identity information provided in the security token did not match data in the connection reply from messaging engine {0} in bus {1}

Explanation

This may indicate that an unauthorized user is attempting to connect to the system.

Action

Check the error logs on the messaging engines involved in the connection attempt.

CWSIT0116E: The security token type of {0} provided by messaging engine {1} in bus {2} for mutual authentication is not supported.

Explanation

Authentication of the remote messaging engine could not be carried out because the security token type is not supported.

Action

Check the error logs on the messaging engines involved in the connection attempt.

CWSIT0117E: The connection reply from messaging engine {0} in bus {1} did not specify a security token type.

Explanation

This might indicate that an unauthorized user is attempting to connect to the system.

Action

Check the error logs on the messaging engines involved in the connection attempt.

CWSIT0118E: During an attempt to connect to a remote messaging engine {0} on bus {1}, incomplete information meant that it was not possible to validate the remote messaging engine""s identity

Explanation

This might have been caused by a timing related issue, or may indicate that an unauthorized user is attempting to connect to the system.

Action

Wait for a retry attempt to be made, or investigate the possibility of a security attack by checking the system and error logs associated with the messaging engines involved in the connection attempt.

CWSIT0119E: A connection attempt was made by remote messaging engine {0} on bus {1}, but incomplete information meant that it was not possible to validate the remote messaging engine""s identity

Explanation

This might have been caused by a timing related issue, or may indicate that an unauthorized user is attempting to connect to the system.

Action

CWSIT0120E: It was not possible to validate the identity of the connecting messaging engine {0} on bus {1}

Explanation

This might have been caused by a timing related issue, or may indicate that an unauthorized user is attempting to connect to the system.

Action

CWSIT0121E: A java.net.UnknownHostException was thrown when attempting to resolve hostname {0}

Explanation

This might have been caused by a client receiving a host name which it could not resolve in Domain Name System, DNS.

Action

Try registering the host name at the local Domain Name Server, or adding an entry to the client"s "hosts" file, then retry the operation.

CWSIT0122W: A static routing table is being used for this cluster - use of static routing normally prevents the service integration bus from functioning correctly and is not recommended.

Explanation

Enabling static routing prevents information such as the location of a messaging engine from being dynamically shared within the cell causing applications to be unable to connect to the bus.

Action

If problems are experienced when using the service integration bus then the static routing table should be deleted and the servers restarted in order to return to the standard routing behavior.

CWSIT0123E: The server is not configured to allow bootstrap for the bus {0}.

Explanation

The client attempted to bootstrap to a bus using a server that was not configured to allow bootstrap for the bus.

Action

Reconfigure the bus so the server can be used for bootstrap, or update the clients provider endpoints to use a different server.

CWSIT0124E: Bus {0} attempted to locate the foreign bus {1} using a server that is not configured to allow bootstrap for the bus {0}.

Explanation

The bus attempted to bootstrap to a foreign bus using a server that does not support bootstrap for the foreign bus.

Action

Reconfigure the bus so that the bootstrap endpoint uses another server by specifying a different host and port combination.

CWSIT9999E: {0}

Explanation

If this message does not give enough information, check the accompanying error messages for further information.

Action

For further information on resolving this error, see the problem determination information on the WebSphere Application Server Support Web page: https://ibm.biz/BdztgV.