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 | CThis 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 | An error occurred while asynchronously reading a client request. There are many reasons this can happen including an HTTP client closing a connection before the server processes the request. Check the exception for more information. |
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 | An error occurred while performing an asynchronous operation. There are many reasons this can happen including an HTTP client closing a connection before the server processes the request. Check the exception for more information. |
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 Web messaging channels have been successfully configured in the channel framework environment for the application server. |
User response | No action is required. |
Problem | A fatal error has occurred. Web messaging applications will not function. |
User response | This error is a fatal error. Review the trace log for any Web container-related error conditions. |
Problem | The Web messaging service has started. You can deploy Web messaging applications on this server. |
User response | No action is required. |
Problem | The configuration file for Web messaging cannot be parsed due to an exception. This problem can occur when the Web messaging configuration file is not specified in valid JavaScript Object Notation(JSON) format. |
User response | Use the exception information to determine the cause of the problem. |
Problem | A servlet that is defined in a configuration file for Web messaging does not exist. |
User response | Verify that the servlet in the configuration file for Web messaging is defined and corresponds to the Web messaging Servlet. |
Problem | The defined servlet in the configuration file for Web messaging is not mapped to the Web messaging Servlet. |
User response | Map the configuration file for Web messaging to the Web messaging servlet. |
Problem | A fatal error occurred when the Web messaging service was initializing the specified identifier. |
User response | For more information, see the associated error messages. |
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 Web messaging client connections. If security is enabled then this problem will prevent Web messaging clients from connecting. |
User response | Ensure that the Web messaging configuration auth alias is correctly configured. |
Problem | If the authentication alias is not specified, default empty string values will be assumed for authentication data required for Web messaging client connections. If security is enabled then this problem will prevent Web messaging clients from connecting. |
User response | Ensure that the Web messaging configuration auth alias is specified. |
Problem | If the incoming Web client cannot be authenticated, default empty string values will be assumed for authentication data required for Web messaging clients. If security is enabled then this problem will prevent Web messaging clients from connecting. |
User response | Ensure that the Web messaging authType configuration option matches currently configured application security values. |
Problem | A failure occurred when closing resources during Web messaging session expiration. Some resources might not be closed properly. |
User response | Refer to specified exception information for the cause. If resources are not being closed, take additional steps to close open resources. |
Problem | A failure occurred when subscribing to the specified channel. The Web messaging client will not received messages for that channel. |
User response | Refer to the specified exception information for the cause. |
Problem | A failure occurred when unsubscribing to the specified channel. The Web messaging client will continue to receive messages for that channel. |
User response | Refer to the specified exception information for the cause. |
Problem | A failure occurred initializing a Web messaging session. Web messaging operations are not available for this client. |
User response | Refer to the specified exception information for the cause. |
Problem | A failure occurred when publishing to the specified channel. The message will not be published. |
User response | Refer to the specified exception information for the cause. |
Problem | A fatal error occurred during Web messaging operations for the specified client. The client needs to start a new Web messaging session to continue Web messaging operations. |
User response | Refer to specified exception information for the cause. |
Problem | Could not read Bayeux request data. No request info will be processed. |
User response | Verify the Bayeux client is sending data as the message parameter of a application/x-www-form-urlencoded encoded POST request. |
Problem | The specified property is not defined with the expected JSON type. |
User response | Modify the specified property in the Web messaging definition to the expected JSON type. |
Problem | The specified property is not defined with the expected JSON type. |
User response | Modify the specified property in the Web messaging definition to the expected JSON type. |
Problem | The specified property needs to be defined. |
User response | Specify a defined value for the property within the Web messaging definition. |
Problem | The specified property needs to be defined. |
User response | Specify a defined value for the property within the Web messaging definition. |
Problem | The specified property must have a string value. |
User response | Specify a string value for the property within the specified Web messaging definition. |
Problem | The specified property must have a string value. |
User response | Specify a string value for the property within the specified Web messaging definition. |
Problem | The value for the specified property must be within the valid range. |
User response | Specify a valid value for the property within the Web messaging definition. |
Problem | The value for the specified property must be within the valid range. |
User response | Specify a valid value for the property within the Web messaging definition. |
Problem | The specified property must be a valid value. |
User response | Specify a valid value for the property within the Web messaging definition. |
Problem | The specified property must be a valid value. |
User response | Specify a valid value for the property within the Web messaging definition. |
Problem | The specified property is required. |
User response | Add the specified property to the Web messaging definition. |
Problem | The specified property is required. |
User response | Add the specified property to the Web messaging definition. |
Problem | You must be able to convert an incoming message to a JSON format. |
User response | Change the message type to a JSON format. |
Problem | An error occurred when processing a Bayeux request. The error code reported corresponds to a Bayeux error code. This code and additional information was also sent to the client. Refer to the Web messaging troubleshooting section of the product documentation for more information. |
User response | Refer to Web messaging service troubleshooting section for error information including corrective actions. |
Problem | An error occurred when a client specified a field with an invalid format. The error code reported corresponds to a Bayeux error code. This code and additional information was also sent to the client. Refer to the Web messaging troubleshooting section of the product documentation for more information. |
User response | Verify the Bayeux client is sending data in the correct format for the specified field. |
Problem | An error occurred when a client specified did not specifiy a required field. The error code reported corresponds to a Bayeux error code. This code and additional informaton was was also sent to the client. Refer to the Web messaging troubleshooting section of the product documentation for more information. |
User response | Verify the Bayeux client is sending data for the required field. |
Problem | The Web messaging servlet received a request when the Web messaging service was unavailable or not configured. |
User response | Verify that the Web messaging service is enabled. Then, verify that the servlet mapping and servlet for the incoming request is configured in the Web application. Finally verify there is an entry in Web messaging configuration file for the incoming request servlet. |
Problem | The application unsuccessfully attempted to locate the Web messaging service. |
User response | Verify that the Web messaging service is installed correctly. For more information, see the product documentation. |
Problem | The Web messaging servlet received a request when the Web messaging service was not available on the server. |
User response | Verify that the Web messaging service is installed correctly. For more information, see the product documentation. |
Problem | Unable to register an asynchronous consumer, refer to the linked exception for more information. |
User response | Obtain a new connection by sending a new handshake request. |
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 message of an incompatible type was consumed from the subscription. This message will be ignored. |
User response | Ensure only Object messages, Text messages and Map messages are published to the topic. |
Problem | The conduit name specified did not start with a / character. |
User response | Ensure the conduit name being used starts with a / character. |
Problem | When using multiple destination format the conduit must take the form /topicSpaceName/subscriptionName. |
User response | Correct the conduit name and retry. |
Problem | When using multiple destination format the conduit must take the form /topicSpaceName/subscriptionName. |
User response | Correct the conduit name and retry. |
Problem | A subscription name must be specified after the leading / character, for example /sports. |
User response | Correct the conduit name and retry. |
Problem | The conduit manager must be initialized before it can be used. |
User response | Ensure that the conduit manager is initialized by performing a handshake before calling other commands. |
Problem | A consumer was not able to be created due to the linked exception. |
User response | Refer to the linked exception for the cause and retry this operation once the problem causing the linked exception is resolved. |
Problem | The user failed authorization when attempting to subscribe to the specified conduit. |
User response | Check the access rights to the messaging engine, the destination and the topic. |
Problem | The user failed authentication when attempting to connect to the messaging engine. |
User response | Check the correct user name has been specified and that the user has access rights to the messaging engine, the destination and the subscription. |
Problem | Unable to initialize a connection to the messaging engine due to an authorization problem. |
User response | Check the correct user name has been specified and that the user has access rights to the messaging engine. |
Problem | It was not possible to create a connection to the messaging engine. |
User response | Refer to the linked exception for the cause and retry this operation once the problem causing the linked exception is resolved. |
Problem | The consumer failed to start, this may be due to connection problems, the connection should no longer be used. |
User response | Obtain a new connection by sending a new handshake request. |
Problem | The consumer failed to stop, this may be due to connection problems, the connection should no longer be used. |
User response | Obtain a new connection by sending a new handshake request. |
Problem | The consumer failed to close, this may be due to connection problems, the connection should no longer be used. |
User response | Obtain a new connection by sending a new handshake request. |
Problem | The consumer failed to close, this may be due to connection problems, the connection should no longer be used. |
User response | Obtain a new connection by sending a new handshake request. |
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 consumer failed to unsubscribe, this may be due to connection problems, the connection should no longer be used. |
User response | Obtain a new connection by sending a new handshake request. |
Problem | The user failed authorization when attempting to publish to the specified conduit. |
User response | Check the access rights to the messaging engine, the destination and the topic. |
Problem | The publish failed due to the linked exception. |
User response | Refer to the linked exception for the cause and retry this operation once the problem causing the linked exception is resolved. |
Problem | The receive failed due to the linked exception. |
User response | Refer to the linked exception for the cause and retry this operation once the problem causing the linked exception is resolved. |
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 subscription could not be created due to the linked exception. |
User response | Refer to the linked exception for the cause and retry this operation once the problem causing the linked exception is resolved. |
Problem | There was no subscription associated with the conduit, so an unsubscribe is not possible. |
User response | Unsubscribe calls should only be performed after a subscription has been created. |
Problem | It is not possible to publish because the destination is not available. |
User response | Refer to the linked exception for the cause and retry this operation once the problem causing the linked exception is resolved. |
Problem | During the validation of the configuration a problem was found, see linked exception for details. |
User response | Correct the configuration and then retry the operation. |
Problem | During the validation of the configuration a required property was not defined. |
User response | Correct the configuration and then retry the operation. |
Problem | The user failed authorization when attempting to publish to the specified conduit. |
User response | Check the access rights to the messaging engine, the destination and the subscription. |
Problem | The publish failed, see the linked exception for more details. |
User response | Refer to the linked exception for the cause of this problem, once resolved retry the operation. |
Problem | A publisher could not be created due to the linked exception. |
User response | Refer to the linked exception for the cause and retry this operation once the problem causing the linked exception is resolved. |
Problem | The bus could does not exist, configuration validation will fail. |
User response | Check the spelling of the bus name in the Web messaging configuration file and check that the bus has been created. |
Problem | The specified property must be defined when the useDistributedSession property has been defined. |
User response | Specify a defined value for the property within the Web messaging definition. |
Problem | A problem occurred when the Web messaging service attempted to look up the DistributedMap reference. For more information, see the associated messages in the log file. |
User response | Ensure that the Web messaging-configured distributedMapRef property is correctly configured |
Problem | The specified durable subscription failed deletion. This may be due to connection problems. The specified durable subscription needs to be deleted administratively. |
User response | Delete the specified durable subscription manually. Determine and fix any problems that are causing durable subscription deletion problems. |
Problem | The time limit has been exceeded when the Web messaging service attempted to reinitialize a Web messaging session. Web messaging operations are not available for this user. |
User response | For more information about the cause of the problem, see the associated messages in the log file. |
Problem | This message is for informational purposes only. |
User response | No action is required. |
Problem | A Web messaging-enabled application has been successfully deployed. |
User response | No action is required. |
Problem | A problem occurred when the Web messaging service attempted to look up an object request broker (ORB) initial reference. The Web messaging service has been disabled. |
User response | Verify that you are using the correct maintenance level and you have installed all of the required fixes. |