Express (Distributed operating systems), v8.0 > Reference > Messages
CWSKA
CWSKA0001E: An internal Web services reliable messaging error occurred in {0}, {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSKA0002E: An internal Web services reliable messaging error occurred in {0}, {1}, related error {2}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSKA0021E: A security exception was raised during reliable messaging processing. Exception: {0}.
Explanation An exception was created by the security component. Action See the accompanying error messages for further information.
CWSKA0022E: A message part named {0} was not secured using the correct security token.
Explanation All messages that reference the reliable messaging sequence must provide proof-of-possession of the security token. Action Ensure that the originator of the message is using an appropriate security configuration. The originator may not be using a valid policyset configuration, such as using WS-ReliableMessaging and WS-SecureConversation instead of a RAMP or RSP policyset. This error may also be caused by an expiry to the security cache. Check the security cache timeouts inside the administrative console.
CWSKA0051E: Unmanaged non-persistent WS-ReliableMessaging store.
Explanation This message is for informational purposes only. Action No action is required.
CWSKA0071E: The sequence identifier {0} has not been found.
Explanation When attempting the operation "writeOutstandingSequenceMessagesToBuffer" the sequence identifier was not found. Action 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.
Explanation 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. Action Ensure the sequence is a request sequence.
CWSKA0101E: A persistent Web services reliable messaging storage manager is not supported in this container.
Explanation A persistent quality of service (QOS) configuration is not supported in the client container. The WS-ReliableMessaging storage manager could not be started. Action Configure the application to use a policy set that specifies an unmanaged quality of service (QOS).
CWSKA0102E: The persistent Web services reliable messaging enabled application could not be initialized because the policy set binding was incomplete or invalid - the bindings file contains bus {0} and messaging engine {1} .
Explanation A managed quality of service configuration requires a policy set binding in order to initialize with a valid messaging engine bus and messaging engine name. Action Configure a policy set binding for the application and assign a valid messaging engine bus and messaging engine name.
CWSKA0103I: Managed persistent store for application with identifier {0}
Explanation This message is for informational purposes only. Action No action is required.
CWSKA0104I: Managed non-persistent store for application with identifier {0}
Explanation This message is for informational purposes only. Action No action is required.
CWSKA0105I: Unmanaged non-persistent store for application with identifier {0}
Explanation This message is for informational purposes only. Action No action is required.
CWSKA0106I: The store cannot connect to the messaging engine {0} on bus {1}.
Explanation This message is for informational purposes only. Action No action is required.
CWSKA0107I: Connected to messaging engine {0} on bus {1}.
Explanation This message is for informational purposes only. Action No action is required.
CWSKA0108E: No connection available to messaging engine {0} on bus {1}.
Explanation An attempt has been made to use the Web services reliable messaging managed quality of service, but the messaging engine is unavailable. Action 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}.
Explanation An attempt has been made to use the Web services reliable messaging managed quality of service, but the messaging engine is unavailable. Action 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
CWSKA0110I: There is a policy set conflict for the parameter {0}, which cannot be set to the values {1} and {2} across services in the same application module
Explanation Services in the same application module that are RM enabled must have the same policy set configuration. Action Either change the policy set configuration or move one of the services into a new application module.
CWSKA0111I: Disabling MakeConnection messages for web service requesters is not supported since the WS-ReliableMessaging version 1.1 synchronous 2-way messaging topology requires this functionality.
Explanation The setting of this property will be ignored. Action Change the policy set configuration to enable the use of MakeConnection messages.
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.
Explanation 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. Action 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.
Explanation 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. Action 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}
Explanation A binding was supplied that contained one or more attributes that were not recognised. Action 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}
Explanation A policy type was supplied that contained one or more attributes that were not recognised. Action 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.
Explanation A Webservices reliable messaging policy was supplied that was not recognised. The supported policy type versions are //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://schemas.xmlsoap.org/ws/2005/02/rm/policy and //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://docs.oasis-open.org/ws-rx/wsrmp/200702 Action Check that the Webservices reliable messaging policy being used contains a supported policy version.
CWSKA0356E: A clustered environment must use a WS-ReliableMessaging managed persistent or managed non-persistent quality of service.
Explanation A web service application has been installed on a cluster and is requesting to use WS-ReliableMessaging, but the quality of service specified is not managed persistent or managed non persistent. Only these qualities of service are supported. Action Alter the attached policyset to use a managed persistent or managed non-persistent quality of service.
CWSKA0357E: WS-Policy has attempted to dynamically configure WS-ReliableMessaging on a Z-series machine or in a clustered environment and so has chosen a managed persistent quality of service but there is no default {0} binding defined.
Explanation 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. When WS-Policy dynamically configures this it requires that there is a default binding defined. Action Check that the specified default binding is defined.
CWSKA0358E: WS-Policy has attempted to dynamically configure WS-ReliableMessaging on a Z-series machine or in a clustered environment and so has chosen a managed persistent quality of service but the default binding {0} does not have a correctly defined WS-ReliableMessaging binding
Explanation 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. When WS-Policy dynamically configures this it requires that there is a default binding defined with a WS-ReliableMessaging binding that contains a valid messaging engine and bus. Action Check that the specified default binding contains a WS-ReliableMessaging binding with valid messaging engine and bus values.
CWSKA0501E: The parameter {0} must not be null for the {1} method.
Explanation The parameter specified must not be null when calling the specified method. Action 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.
Explanation 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. Action 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.
Explanation The target provider endpoint URI must not be null when trying to establish a new Web services reliable messaging sequence. Action 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.
Explanation 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. Action Ensure that all transactions are committed prior to invoking "waitUntilSequenceCompleted".
CWSKA0505E: Web services reliable messaging is not enabled for this application.
Explanation An application has tried to use Web services reliable messaging, but reliable messaging is not enabled for this application. Action 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}.
Explanation 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. Action 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.
Explanation 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. Action 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.
Explanation 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. Action 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}
Explanation 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. Action 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 "//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://schemas.xmlsoap.org/ws/2005/02/rm/policy" version of the reliable messaging specification, so the sequence has not been closed.
Explanation The closeSequence request is only supported in v1.1 of the reliable messaging specification. The application is using v1.0 of the specification so no action is undertaken in the reliable messaging runtime. Action Either remove the call to closeSequence from the application, or update the policy set to use v1.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.
Explanation Certain message exchange patterns, such as two-way request-reply messaging, do not support transactional updates to the Web services reliable messaging storage manager. Action Check the message exchange pattern 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 the application has a transaction at the time of sending.
Explanation Transactional sends enlist the Web services reliable messaging storage manager in the application's transactional context. If the application does not have a transactional context then this cannot be done. Action Either ensure the 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.
Explanation 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. Action Either change to managedPersitent or managedNonPersistent quality of service or change the application to perform non transactional sends.
CWSKA0651E: Web services reliable messaging does not support SOAP over JMS.
Explanation An application has tried to use Web services reliable messaging over a JMS transport, but this is not supported. Action Either remove Web services reliable messaging from the policy set of the application or use an HTTP transport for the SOAP messages.
CWSKA0701W: A persistent web services reliable messaging sequence for a request-response web service has been recovered: this sequence might require administrative action.
Explanation Request-response sequences with stored persistent messages cannot be automatically re-sent at application startup. Action Use the administration console to either terminate the WS-ReliableMessaging sequence or to reallocate any stored messages.
CWSKA0751W: A web services reliable messaging sequence with ID {0} has unacknowledged messages at the time of the JVM shutting down.
Explanation Some messages not have been acknowledged by the web services reliable messaging destination. These messages may not have been sent before the JVM shuts down. Action Change the application code to make a blocking call to the web services reliable SPI or deploy the code in the server environment.
CWSKA0801E: The combine assertions method has been called without any assertions to combine.
Explanation An attempt has been made to intersect two WS-Policy assertions which has failed. Action Ensure that the web services reliable messaging policy sets have been applied correctly.
CWSKA0802E: The combine assertions method has been called with two serverside policy set assertions.
Explanation An attempt has been made to intersect two WS-Policy assertions which has failed. Action Ensure that the web services reliable messaging policy sets have been applied correctly.
CWSKA0803E: The combine assertions method has been called with two clientside policy set assertions.
Explanation An attempt has been made to intersect two WS-Policy assertions which has failed. Action Ensure that the web services reliable messaging policy sets have been applied correctly.
CWSKA0804E: The client configuration transform has been called with an unsupported Web services reliable messaging policy :{0}. This will be ignored.
Explanation An attempt has been made to transform a WS-Policy policy and an unsupported policy has been found. Action Ensure that the web services reliable messaging policy sets have been applied correctly.
CWSKA0805E: Web services reliable messaging cannot be dynamically engaged using WS-Policy, for the application {0} in this environment without a policy set binding attatched.
Explanation Web services reliable messaging has been engaged due to a WS-Policy exchange. However, when running in a cluster or on zOS, web services reliable messaging must be configured to use a managed quality of service. This requires user action. Action Attach a web services reliable messaging policy set to the application. Ensure this policy set specifies a managed quality of service.
CWSKA9999E: {0}
Explanation If the message does not give sufficient information, check the accompanying messages. Action See the accompanying error messages for further information.