CWPSB

CWPSB0001E: The Web messaging channel caught the following unexpected exception: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/.
CWPSB1022E: The Web messaging channel caught the following unexpected exception from the asynchronous getRequestBodyBuffers method: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/.
CWPSB1023E: The Web messaging channel caught the following unexpected exception from the synchronous getRequestBodyBuffers method: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/.
CWPSB1024E: The Web messaging channel caught the following unexpected exception from the discriminate method: {0}
Explanation CThis exception is unexpected. The cause is not immediately known.
Action 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/.
CWPSB1025E: The Web messaging channel caught the following unexpected exception during an asynchronous read operation: {0}
Explanation 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.
Action 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/.
CWPSB1026E: The Web messaging service caught the following unexpected exception while creating the Web message acceptor channel: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/.
CWPSB1027E: The Web messaging channel caught the following unexpected exception while attempting to delegate a Web messaging request to the Web message container: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/.
CWPSB1028W: The Web messaging channel caught the following unexpected exception when it performed asynchronous operations: {0}
Explanation 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.
Action 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/.
CWPSB1029E: The Web message channel cannot access the ChannelFramework Service.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/.
CWPSB1030I: The Web messaging channels have been configured.
Explanation The Web messaging channels have been successfully configured in the channel framework environment for the application server.
Action No action is required.
CWPSB1101E: The Web Container Service and Web messaging applications are unavailable.
Explanation A fatal error has occurred. Web messaging applications will not function.
Action This error is a fatal error. Review the trace log for any Web container-related error conditions.
CWPSB1102I: The Web messaging service has started.
Explanation The Web messaging service has started. You can deploy Web messaging applications on this server.
Action No action is required.
CWPSB1103E: The Web messaging service cannot parse the {0} Web messaging configuration file for the {1} context root. The following exception occurred: {2}.
Explanation 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.
Action Use the exception information to determine the cause of the problem.
CWPSB1151E: The following error occurred in the Web messaging configuration file for the context root: {0}. The Web messaging service cannot find the {1} servlet.
Explanation A servlet that is defined in a configuration file for Web messaging does not exist.
Action Verify that the servlet in the configuration file for Web messaging is defined and corresponds to the Web messaging Servlet.
CWPSB1152E: An error occurred in the Web messaging Configuration file for the {0} context root. The {1} servlet is not mapped to the {2} servlet class.
Explanation The defined servlet in the configuration file for Web messaging is not mapped to the Web messaging Servlet.
Action Map the configuration file for Web messaging to the Web messaging servlet.
CWPSB1153E: A Web messaging initialization error occurred for the {0} identifier. Web messaging operations are not available for this definition.
Explanation A fatal error occurred when the Web messaging service was initializing the specified identifier.
Action For more information, see the associated error messages.
CWPSB1201W: Unable to obtain authentication data from Web messaging configured authentication alias {0} for definition {1}.
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 Web messaging client connections. If security is enabled then this problem will prevent Web messaging clients from connecting.
Action Ensure that the Web messaging configuration auth alias is correctly configured.
CWPSB1202W: No authentication alias has been specified for Web messaging definition {0}.
Explanation 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.
Action Ensure that the Web messaging configuration auth alias is specified.
CWPSB1203W: Could not authenticate incoming user using {0} credentials for Web messaging definition {1}.
Explanation 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.
Action Ensure that the Web messaging authType configuration option matches currently configured application security values.
CWPSB1207E: Web messaging session expiration failure for user {0} in Web messaging definition {1}. Exception: {2}
Explanation A failure occurred when closing resources during Web messaging session expiration. Some resources might not be closed properly.
Action Refer to specified exception information for the cause. If resources are not being closed, take additional steps to close open resources.
CWPSB1208E: Subscription failure on channel {0} for user {1} in Web messaging definition {2}. Exception: {3}
Explanation A failure occurred when subscribing to the specified channel. The Web messaging client will not received messages for that channel.
Action Refer to the specified exception information for the cause.
CWPSB1209E: Unsubscribe failure on channel {0} for user {1} in Web messaging definition {2}. Exception: {3}
Explanation A failure occurred when unsubscribing to the specified channel. The Web messaging client will continue to receive messages for that channel.
Action Refer to the specified exception information for the cause.
CWPSB1210E: Web messaging session initialization failure for user {0} in Web messaging definition {1}. Exception: {2}
Explanation A failure occurred initializing a Web messaging session. Web messaging operations are not available for this client.
Action Refer to the specified exception information for the cause.
CWPSB1211E: Publish failure on channel {0} for user {1} in Web messaging definition {2}. Exception: {3}
Explanation A failure occurred when publishing to the specified channel. The message will not be published.
Action Refer to the specified exception information for the cause.
CWPSB1212E: Fatal Web messaging operation error for user {0} in Web messaging definition {1}. Exception: {2}
Explanation 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.
Action Refer to specified exception information for the cause.
CWPSB1213E: Error reading Bayeux request content. Exception: {1}
Explanation Could not read Bayeux request data. No request info will be processed.
Action Verify the Bayeux client is sending data as the message parameter of a application/x-www-form-urlencoded encoded POST request.
CWPSB1301E: The {0} Web messaging definition for the {1} property is not a valid {2} JavaScript Object Notation (JSON) type.
Explanation The specified property is not defined with the expected JSON type.
Action Modify the specified property in the Web messaging definition to the expected JSON type.
CWPSB1302W: The {0} Web messaging definition for the {1} property is not a valid {2} JavaScript Object Notation (JSON) type. This property will be set to the default value.
Explanation The specified property is not defined with the expected JSON type.
Action Modify the specified property in the Web messaging definition to the expected JSON type.
CWPSB1303E: The {1} property for the {0} Web messaging definition does not have a defined value.
Explanation The specified property needs to be defined.
Action Specify a defined value for the property within the Web messaging definition.
CWPSB1304W: The {1} property for the {0} Web messaging definition does not have a defined value. This property will be set to the default value.
Explanation The specified property needs to be defined.
Action Specify a defined value for the property within the Web messaging definition.
CWPSB1305E: The {1} property for the {0} Web messaging definition cannot be a blank String.
Explanation The specified property must have a string value.
Action Specify a string value for the property within the specified Web messaging definition.
CWPSB1306W: The {1} property for the {0} Web messaging definition cannot be a blank String. This property will be set to the default value.
Explanation The specified property must have a string value.
Action Specify a string value for the property within the specified Web messaging definition.
CWPSB1307E: The {1} property for the {0} Web messaging definition has a {2} value. This value is not a valid value within the {3} to {4} range.
Explanation The value for the specified property must be within the valid range.
Action Specify a valid value for the property within the Web messaging definition.
CWPSB1308W: The {1} property for the {0} Web messaging definition has a {2} value. This value is not a valid value within the {3} to {4} range. This property will be set to the default value.
Explanation The value for the specified property must be within the valid range.
Action Specify a valid value for the property within the Web messaging definition.
CWPSB1309E: The {1} property for the {0} Web messaging definition specifies the {2} value. This value is not listed in allowed values {2}.
Explanation The specified property must be a valid value.
Action Specify a valid value for the property within the Web messaging definition.
CWPSB1310W: The {1} property for the {0} Web messaging definition specifies the {2} value. This value is not listed in allowed values {2}. This property will be set to the default value.
Explanation The specified property must be a valid value.
Action Specify a valid value for the property within the Web messaging definition.
CWPSB1311E: The {1} property for the {0} Web messaging definition is required.
Explanation The specified property is required.
Action Add the specified property to the Web messaging definition.
CWPSB1312W: The {1} property for the {0} Web messaging definition is required. This property will be set to the default value.
Explanation The specified property is required.
Action Add the specified property to the Web messaging definition.
CWPSB1313W: The consumer received a message of the {0} type. However, the Web messaging service cannot convert the message to a suiteable JavaScript Object Notation (JSON) format. The Web messaging service cannot send the message to any clients.
Explanation You must be able to convert an incoming message to a JSON format.
Action Change the message type to a JSON format.
CWPSB1314W: Bayeux error {0} occurred when processing a Bayeux request for channel {1} with arguments {2} in Web messaging definition {3}.
Explanation 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.
Action Refer to Web messaging service troubleshooting section for error information including corrective actions.
CWPSB1315W: Bayeux error {0} occurred when processing a Bayeux request for channel {1} with arguments {2} in Web messaging definition {3}. Field {4} was not specified in format {5}.
Explanation 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.
Action Verify the Bayeux client is sending data in the correct format for the specified field.
CWPSB1316W: Bayeux error {0} occurred when processing a Bayeux request for channel {1} with arguments {2} in Web messaging definition {3}. Field {4} is required.
Explanation 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.
Action Verify the Bayeux client is sending data for the required field.
CWPSB1701E: The Web messaging service is not configured for the following incoming URI: {0}
Explanation The Web messaging servlet received a request when the Web messaging service was unavailable or not configured.
Action 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.
CWPSB1702E: The application failed to locate the Web messaging service. Web messaging operations for this application are not possible.
Explanation The application unsuccessfully attempted to locate the Web messaging service.
Action Verify that the Web messaging service is installed correctly. For more information, see the product documentation.
CWPSB1703E: Web messaging service operations are not available for the following incoming URI: {0}
Explanation The Web messaging servlet received a request when the Web messaging service was not available on the server.
Action Verify that the Web messaging service is installed correctly. For more information, see the product documentation.
CWPSB4001E: The registration of an asynchronous consumer for the conduit {0} failed with exception: {1}.
Explanation Unable to register an asynchronous consumer, refer to the linked exception for more information.
Action Obtain a new connection by sending a new handshake request.
CWPSB4002E: Unable to serialize the object message being consumed when consuming from the subscription {0}.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/.
CWPSB4003E: Unsupported message type {0}, only Object messages, Text messages and Map messages are supported. The message was published to {1}. The message will be ignored, message data: {2}
Explanation A message of an incompatible type was consumed from the subscription. This message will be ignored.
Action Ensure only Object messages, Text messages and Map messages are published to the topic.
CWPSB4100E: Conduit must start with a / character.
Explanation The conduit name specified did not start with a / character.
Action Ensure the conduit name being used starts with a / character.
CWPSB4101E: Conduit does not contain a / character to separate the destination from the subscription.
Explanation When using multiple destination format the conduit must take the form /topicSpaceName/subscriptionName.
Action Correct the conduit name and retry.
CWPSB4102E: Conduit contains a destination but not a subscription.
Explanation When using multiple destination format the conduit must take the form /topicSpaceName/subscriptionName.
Action Correct the conduit name and retry.
CWPSB4103E: Conduit does not contain a subscription.
Explanation A subscription name must be specified after the leading / character, for example /sports.
Action Correct the conduit name and retry.
CWPSB4104E: Conduit manager has not been initialized, can not call {0}. A handshake must be called prior to calling other methods
Explanation The conduit manager must be initialized before it can be used.
Action Ensure that the conduit manager is initialized by performing a handshake before calling other commands.
CWPSB4105E: Unable to create a consumer for conduit {0} while attempting to create a subscription. Linked Exception: {1}
Explanation A consumer was not able to be created due to the linked exception.
Action Refer to the linked exception for the cause and retry this operation once the problem causing the linked exception is resolved.
CWPSB4106E: Unable to create a consumer for conduit {0} due to the authorization error: {1}.
Explanation The user failed authorization when attempting to subscribe to the specified conduit.
Action Check the access rights to the messaging engine, the destination and the topic.
CWPSB4107E: Unable to create a connection to the messaging engine for conduit {0} due to the authentication error: {1}.
Explanation The user failed authentication when attempting to connect to the messaging engine.
Action Check the correct user name has been specified and that the user has access rights to the messaging engine, the destination and the subscription.
CWPSB4108E: Unable to create a connection to the messaging engine for conduit {0} due to the authorization error: {1}.
Explanation Unable to initialize a connection to the messaging engine due to an authorization problem.
Action Check the correct user name has been specified and that the user has access rights to the messaging engine.
CWPSB4109E: Unable to create a connection to the messaging engine for conduit {0} due to the error: {1}.
Explanation It was not possible to create a connection to the messaging engine.
Action Refer to the linked exception for the cause and retry this operation once the problem causing the linked exception is resolved.
CWPSB4110E: Failed to start the consumer for conduit {1}, see linked exception for more information: {0}
Explanation The consumer failed to start, this may be due to connection problems, the connection should no longer be used.
Action Obtain a new connection by sending a new handshake request.
CWPSB4111E: Failed to stop the consumer for conduit {1}, see linked exception for more information: {0}
Explanation The consumer failed to stop, this may be due to connection problems, the connection should no longer be used.
Action Obtain a new connection by sending a new handshake request.
CWPSB4112E: Failed to close the consumer for conduit {1}, see linked exception for more information: {0}
Explanation The consumer failed to close, this may be due to connection problems, the connection should no longer be used.
Action Obtain a new connection by sending a new handshake request.
CWPSB4113E: Failed to close the connection, see linked exception for more information: {0}
Explanation The consumer failed to close, this may be due to connection problems, the connection should no longer be used.
Action Obtain a new connection by sending a new handshake request.
CWPSB4114E: An empty or null topic name passed to ConduitManagerImpl.allocateConduitMessageID.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/.
CWPSB4115E: No such registered topic. A conduit message id cannot be allocated for conduit {0}.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/.
CWPSB4116E: Failed to unsubscribe the consumer for conduit {0} due to {1}
Explanation The consumer failed to unsubscribe, this may be due to connection problems, the connection should no longer be used.
Action Obtain a new connection by sending a new handshake request.
CWPSB4117E: Unable to publish for conduit {0} due to the authorization error: {1}
Explanation The user failed authorization when attempting to publish to the specified conduit.
Action Check the access rights to the messaging engine, the destination and the topic.
CWPSB4118E: Unable to publish for conduit {0} due to the error: {1}
Explanation The publish failed due to the linked exception.
Action Refer to the linked exception for the cause and retry this operation once the problem causing the linked exception is resolved.
CWPSB4119E: Unable to receive from conduit {0} due to the error: {1}
Explanation The receive failed due to the linked exception.
Action Refer to the linked exception for the cause and retry this operation once the problem causing the linked exception is resolved.
CWPSB4120E: The method {0} is not supported.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/.
CWPSB4121E: Unable to create a consumer for conduit {0} as the destination was not reachable or not available. Linked Exception: {1}
Explanation A subscription could not be created due to the linked exception.
Action Refer to the linked exception for the cause and retry this operation once the problem causing the linked exception is resolved.
CWPSB4122E: Unable to unsubscribe from conduit {0} as the conduit does not have a subscription.
Explanation There was no subscription associated with the conduit, so an unsubscribe is not possible.
Action Unsubscribe calls should only be performed after a subscription has been created.
CWPSB4123E: Unable to publish on conduit {0} as the destination was not reachable or not available. Linked Exception: {1}
Explanation It is not possible to publish because the destination is not available.
Action Refer to the linked exception for the cause and retry this operation once the problem causing the linked exception is resolved.
CWPSB4150E: The configuration validation for the service integration bus failed with exception {0}
Explanation During the validation of the configuration a problem was found, see linked exception for details.
Action Correct the configuration and then retry the operation.
CWPSB4151E: The Web Messaging definition {0} was missing the required property {1}.
Explanation During the validation of the configuration a required property was not defined.
Action Correct the configuration and then retry the operation.
CWPSB4152E: Unable to publish to the conduit {0} due to the authorization error: {1}
Explanation The user failed authorization when attempting to publish to the specified conduit.
Action Check the access rights to the messaging engine, the destination and the subscription.
CWPSB4153E: Unable to publish to the conduit {0} due to the error: {1}
Explanation The publish failed, see the linked exception for more details.
Action Refer to the linked exception for the cause of this problem, once resolved retry the operation.
CWPSB4154E: Unable to create a publisher for conduit {0} as the destination was not reachable or not available. Linked Exception: {1}
Explanation A publisher could not be created due to the linked exception.
Action Refer to the linked exception for the cause and retry this operation once the problem causing the linked exception is resolved.
CWPSB4160E: The Web messaging definition {1} refers to the bus {0}, but this bus does not exist.
Explanation The bus could does not exist, configuration validation will fail.
Action Check the spelling of the bus name in the Web messaging configuration file and check that the bus has been created.
CWPSB5000E: The {1} property for the {0} Web messaging definition does not have a defined value.
Explanation The specified property must be defined when the useDistributedSession property has been defined.
Action Specify a defined value for the property within the Web messaging definition.
CWPSB5001E: The Web messaging service cannot obtain a reference from the {0} Web messaging configured DistributedMap for the {1} definition because of the following exception: {2}
Explanation 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.
Action Ensure that the Web messaging-configured distributedMapRef property is correctly configured
CWPSB5002E: The Web messaging service cannot delete the {0} durable subscription on the {1} messaging engine. For more information, see the following exception: {2}
Explanation The specified durable subscription failed deletion. This may be due to connection problems. The specified durable subscription needs to be deleted administratively.
Action Delete the specified durable subscription manually. Determine and fix any problems that are causing durable subscription deletion problems.
CWPSB5003E: The time limit for reinitializing Web messaging has been exceeded for the {0} user in the {1} Web messaging definition.
Explanation 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.
Action For more information about the cause of the problem, see the associated messages in the log file.
CWPSB5004I: The Web messaging service is at the {0} build level.
Explanation This message is for informational purposes only.
Action No action is required.
CWPSB5005I: The {0} Web messaging service definition initialized successfully.
Explanation A Web messaging-enabled application has been successfully deployed.
Action No action is required.
CWPSB5006E: An initialization failure has occurred when Web messaging service attempted to resolve the {0} initial reference. For more information, see the following exception: {1}
Explanation 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.
Action Verify that you are using the correct maintenance level and you have installed all of the required fixes.
Reference topic    

Terms and conditions for information centers | Feedback

Last updated: May 16, 2012 4:38:33 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.webmsg.resources.Messages.html

© Copyright IBM Corporation 2006, 2011. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)