Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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. |
Problem | 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/. |
Problem | 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/. |
Problem | 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. |
User response | 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. |
Problem | 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. |
User response | 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. |
Problem | 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. |
User response | 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. |
Problem | 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. |
User response | Ask your system administrator to investigate the logs for the application server to help determine the reason for the failure. |
Problem | 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. |
Problem | 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. |
Problem | 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/. |
Problem | 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/. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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/. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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/. |
Problem | 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. |
Problem | A messaging engine to messaging engine connection has been started. |
User response | No action required. |
Problem | A messaging engine to messaging engine connection has been stopped. |
User response | No action required. |
Problem | A messaging engine to messaging engine intra-bus connection has been started. |
User response | No action required. |
Problem | A messaging engine to messaging engine intra-bus connection has been stopped. |
User response | No action required. |
Problem | A messaging engine to messaging engine inter-bus connection has been started. |
User response | No action required. |
Problem | A messaging engine to messaging engine inter-bus connection has been stopped. |
User response | No action required. |
Problem | 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. |
Problem | 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. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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/. |
Problem | 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/. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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. |
Problem | 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/. |
Problem | 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/. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | A client could not be attached to the bus because there are no messaging engines in the required bus running 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. |
Problem | 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. |
Problem | A client attempted to send a bootstrap request to connect to a bus, but the bus does not permit bootstrap requests using that channel. |
User response | Reconfigure the client so that the bootstrap endpoint uses a permitted chain. |
Problem | When a service integration bus authentication alias is not configured on a service integration bus link it is possible to create an inter-bus link between a secure bus and an insecure bus without carrying out an authentication check. |
User response | Configure the service integration bus link authentication alias if you wish to enforce an authentication check. |
Problem | A client attempted to send a request to connect to a bus, but the bus does not permit connections using that channel chain. |
User response | Reconfigure the client so that it connects using a permitted chain. |
Problem | A bus attempted to use a bootstrap transport chain that is not supported by the foreign bus. |
User response | Reconfigure the bus so that the bootstrap endpoint uses a chain permitted by the foreign bus. |
Problem | The user ID used to create a connection with a the bus was not authorized to connect to the bus. |
User response | Ensure that the user id has the bus connector role for the bus. |
Problem | A bus attempted to use an inbound transport chain that is not supported by the foreign bus. |
User response | Reconfigure the bus so that it connects on a chain permitted by the foreign bus. |
Problem | The bus has been configured to use a transport channel chain that is not permitted for communication between messaging engines. |
User response | Reconfigure the bus so that it specifies a permitted chain as the inter-engine transport chain. |
Problem | The bus attempted to use a transport channel chain that is not permitted. |
User response | Reconfigure the bus so that it connects on a permitted transport channel chain. |
Problem | 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. |
Problem | 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. |
User response | Ask your system administrator to investigate the logs for the messaging engine to help determine the reason for the problem. |
Problem | The request to resolve a target MessagingEngine failed. |
User response | Ask your system administrator to investigate the logs for the messaging engine to help determine the reason for the problem. |
Problem | The request to resolve a target MessagingEngine failed. |
User response | Ask your system administrator to investigate the logs for the messaging engine to help determine the reason for the problem. |
Problem | The request to resolve a target MessagingEngine failed. |
User response | Ask your system administrator to investigate the logs for the messaging engine to help determine the reason for the problem. |
Problem | The request to resolve a target MessagingEngine failed. |
User response | Ask your system administrator to investigate the logs for the messaging engine to help determine the reason for the problem. |
Problem | The MessagingEngine exists but is not started. |
User response | Ask your system administrator to investigate the logs for the messaging engine to help determine the reason for the problem. |
Problem | Authentication with the remote messaging engine failed because the application did not specify a user ID. |
User response | Ensure that both the user ID and password values are correct. |
Problem | A bridge has been established with another messaging engine in a different bus. |
User response | No action required. |
Problem | Use of the specified port results in the default choice of an insecure transport chain because the chain name was not specified in the provider endpoint. The user should be aware of the implications that this default has for security. |
User response | 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. |
Problem | 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. |
User response | Ensure that both the user ID and password values are correct. |
Problem | Authorization with the remote messaging engine failed because the application did not specify a user ID. |
User response | Ensure that both the user ID and password values are correct. |
Problem | 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. |