WebSphere Process Server messages     Operating Systems: All supported

CWSKA

CWSKA0001E: An internal Web services reliable messaging error occurred in {0}, {1}
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/.
CWSKA0002E: An internal Web services reliable messaging error occurred in {0}, {1}, related error {2}
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/.
CWSKA0021E: A security exception was raised during reliable messaging processing. Exception: {0}.
Problem An exception was thrown by the security component.
User response See the accompanying error messages for further information.
CWSKA0022E: A message part named {0} was not secured using the correct security token.
Problem All messages that reference the reliable messaging sequence must provide proof-of-possession of the security token.
User response Ensure that the originator of the message is using an appropriate security configuration.
CWSKA0051E: Unmanaged non-persistent WS-ReliableMessaging store.
Problem This message is for informational purposes only.
User response No action is required.
CWSKA0071E: The sequence identifier {0} has not been found.
Problem When attempting the operation "writeOutstandingSequenceMessagesToBuffer" the sequence identifier was not found.
User response Ensure the sequence exists in the administrative console for the application.
CWSKA0072E: The sequence {0} could not be reallocated as it is a response message sequence. Only request message sequences can be reallocated.
Problem It is not permitted to reallocate messages from one Web services Reliable Messaging sequence to another if the sequence contains application response messages for a two-way operation.
User response Ensure the sequence is a request sequence.
CWSKA0101E: A managed Web services reliable messaging storage manager is not supported in this container.
Problem A managed quality of service (QOS) configuration is not supported in the client container. The WS-ReliableMessaging storage manager could not be started.
User response Configure the application to use a policy set that specifies an unmanaged quality of service (QOS).
CWSKA0102E: The managed Web services reliable messaging storage manager could not be initialized because the policy set binding was incomplete or invalid.
Problem A managed quality of service (QOS) configuration requires a policy set binding in order to initialize.
User response Configure a policy set binding for the application.
CWSKA0103I: Managed persistent store for application with identifier {0}
Problem This message is for informational purposes only.
User response No action is required.
CWSKA0104I: Managed non-persistent store for application with identifier {0}
Problem This message is for informational purposes only.
User response No action is required.
CWSKA0105I: Unmanaged non-persistent store for application with identifier {0}
Problem This message is for informational purposes only.
User response No action is required.
CWSKA0106I: The store cannot connect to the messaging engine {0} on bus {1}.
Problem This message is for informational purposes only.
User response No action is required.
CWSKA0107I: Connected to messaging engine {0} on bus {1}.
Problem This message is for informational purposes only.
User response No action is required.
CWSKA0108E: No connection available to messaging engine {0} on bus {1}.
Problem An attempt has been made to use the Web services reliable messaging managed quality of service, but the messaging engine is unavailable.
User response Ensure that the correct messaging engine and bus names are being specified and check that the messaging engine has been started.
CWSKA0109W: No connection available to messaging engine {0} on bus {1} for application {2}.
Problem An attempt has been made to use the Web services reliable messaging managed quality of service, but the messaging engine is unavailable.
User response Ensure that the correct messaging engine and bus names are being specified and check that the messaging engine has been started. This message is a warning and attempts to connect to the messaging engine will be made
CWSKA0351E: The Web services reliable messaging managed persistent and managed non-persistent qualities of service require a service integration bus and messaging engine to be set.
Problem When using the managed persistent or the managed non-persistent quality of service for reliable messaging, the application needs to be bound to a messaging engine and bus.
User response Check that the reliable messging bindings for the application have been defined and contain a valid bus and bus member.
CWSKA0352E: The Web services reliable messaging unmanaged non-persistent quality of service is not allowed when running in an application server on a Z-series machine.
Problem The unmanaged non-persistent quality of service for reliable messaging cannot be associated with an application running inside an application server hosted on a Z-series machine.
User response For applications running inside an application server on a Z-series machine, use a managed persistent or managed non-persistent quality of service.
CWSKA0353E: One or more of the attributes specified in the binding were not recognised: {0}
Problem A binding was supplied that contained one or more attributes that were not recognised.
User response Check each attribute specified in the binding and ensure that it is a valid WS-ReliableMessaging binding attribute.
CWSKA0354E: One or more of the attributes specified in the policy type were not recognised: {0}
Problem A policy type was supplied that contained one or more attributes that were not recognised.
User response Check each attribute specified in the policy type and ensure that it is a valid WS-ReliableMessaging policy type attribute.
CWSKA0355E: Webservices reliable messaging failed to load the policy as the policy version was not recognised.
Problem A Webservices reliable messaging policy was supplied that was not recognised. The supported policy type versions are http://schemas.xmlsoap.org/ws/2005/02/rm/policy and http://docs.oasis-open.org/ws-rx/wsrmp/200702
User response Check that the Webservices reliable messaging policy being used contains a supported policy version.
CWSKA0501E: The parameter {0} must not be null for the {1} method.
Problem The parameter specified must not be null when calling the specified method.
User response Update the application to provide a non-null value for the specified parameter.
CWSKA0502E: The supplied parameter value for clientObject {0} is not a known type.
Problem The supplied parameter value for clientObject is not a known type. The clientObject needs to be an instance of either a JAX-WS Dispatch or a dynamic proxy client.
User response Ensure that the parameter value supplied to the method call is either a instance of the Dispatch class, or an instance of the dynamic proxy.
CWSKA0503E: The target provider endpoint URI is null.
Problem The target provider endpoint URI must not be null when trying to establish a new Web services reliable messaging sequence.
User response Update the application to provide a non-null value for the target provider endpoint URI in the WSRMSequenceProperties.
CWSKA0504E: Unable to issue "waitUntilSequenceCompleted" for the target provider endpoint URI {0} as there is an uncommitted transaction for the sequence.
Problem A call has been made to the API method "waitUntilSequenceCompleted" which can not complete as there is a transaction for the specified sequence which has not been committed. This is normally due to the application being installed inside the EJB container and using container managed transactions. In this case the invoke for the target endpoint and "waitUntilSequenceCompleted" can not occur inside the same transaction.
User response Ensure that all transactions are committed prior to invoking "waitUntilSequenceCompleted".
CWSKA0505E: Web services reliable messaging is not enabled for this application.
Problem An application has tried to use Web services reliable messaging, but reliable messaging is not enabled for this application.
User response Assign a Web services reliable messaging policy set to the application.
CWSKA0506E: A Web services reliable messaging sequence has not been found for endpoint URI {0}.
Problem An application has tried to use a Web services reliable messaging sequence, but no sequence has been found between this application and the target endpoint URI. The client might have previously terminated the sequence, the sequence might have timed out, or the sequence is non-persistent and the client application has been restarted.
User response Use the administrative console to check the status of the Web services reliable messaging sequence for the application.
CWSKA0507E: An application has tried to use a Web services reliable messaging sequence to target endpoint URI {0}, this sequence has been terminated.
Problem An application has tried to use a Web services reliable messaging sequence that has previously been terminated. The client might have previously terminated the sequence, the sequence might have timed out, or the sequence is non-persistent and the client application has been restarted.
User response Use the administrative console to check the status of the Web services reliable messaging sequence for the application.
CWSKA0508E: An application has attempted to use a Web services reliable messaging sequence to target endpoint URI {0}, this sequence has been closed.
Problem An application has attempted to use a Web services reliable messaging sequence that has previously been closed. The client might have previously closed the sequence.
User response Use the administrative console to check the status of the Web services reliable messaging sequence for the application.
CWSKA0509E: An existing Web services reliable messaging sequence has been found for endpoint URI {0}
Problem An application has attempted to create a Web services reliable messaging sequence to a target endpoint URI for which a sequence already exists. The client might have previously created the sequence.
User response Use the administrative console to check the status of the Web services reliable messaging sequence for the application.
CWSKA0510W: An application has tried to use the closeSequence request to close a Web services reliable messaging sequence to endpoint URI {0}. This application is using the "http://schemas.xmlsoap.org/ws/2005/02/rm/policy" version of the reliable messaging specification, so the sequence has not been closed.
Problem The closeSequence request is only supported in Version 1.1 of the reliable messaging specification. The application is using Version 1.0 of the specification so no action is undertaken in the reliable messaging runtime.
User response Either remove the call to closeSequence from the application, or update the policy set to use Version 1.1 of the reliable messaging specification.
CWSKA0551E: The message with ID {0} to service {1} cannot be processed within a transaction because transactional updates to the Web services reliable messaging storage manager are not allowed in this message exchange pattern. Only one-way messages are allowed to be sent transactionally.
Problem Certain message exchange patterns, such as two-way request-reply messaging, do not support transactional updates to the Web services reliable messaging storage manager.
User response Check the message exchange pattern that is used for the specified service and ensure that transactional updates are supported.
CWSKA0552E: The message with ID {0} to service {1} cannot be processed within a transaction because there is no transaction context available. Please ensure that your application has a transaction at the time of sending.
Problem Transactional sends enlist the Web services reliable messaging storage manager in the application's transactional context. If your application does not have a transactional context then this cannot be done.
User response Either ensure your application has a transactional context at the time of putting or change to a non-transactional put.
CWSKA0553E: The message with ID {0} to service {1} cannot be processed within a transaction because you are not using a managed Web services reliable messaging storage manager.
Problem Transactional sends enlist the Web services reliable messaging storage manager in the application's transactional context, but can only do this if the application's configuration selects a managed store.
User response Either change to managedPersitent or managedNonPersistent quality of service or change the application to perform non transactional sends.
CWSKA9999E: {0}
Problem If the message does not give sufficient information, check the accompanying messages.
User response See the accompanying error messages for further information.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.websvcs.rm.CWSKAMessages.html

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