Express (Distributed operating systems), v8.0 > Reference > Messages
CWPOL
CWPOL0000E: The client cannot acquire the policy of the provider service at URI {0} using an HTTP GET request because the following exception occured {1}.
Explanation The client is configured to use the policy of the provider service specified in the message using an HTTP GET request, but the request resulted in an exception. Action Ensure that the endpoint address is correct and that the endpoint supports HTTP GET. The exception in the message may contain information to help diagnose the problem.
CWPOL0001E: The client could not process the policy set {1} and policy set binding {2} configured for the HTTP GET request to retrieve the WSDL for the provider service at URI {0} because the following exception occured {3}.
Explanation The client is configured to acquire the policy of the provider service using a HTTP GET request with transport level policy, but either the policy set or the binding specified to secure the request is not valid. Action Reconfigure the client and specify a valid policy set and binding for the HTTP GET request.
CWPOL0002E: The client cannot acquire the policy of the provider service at URI {0} using a WS-MetadataExchange GetMetadata request because the following exception occurred {1}.
Explanation The client is configured to use the policy of the provider service specified in the message using a WS-MetadataExchange request, but the request resulted in an exception. Action Ensure that the endpoint address is correct, that the endpoint supports WS-MetadataExchange, and that the endpoint and client have compatible security configurations. The exception in the message may contain information to help diagnose the problem.
CWPOL0003E: The client cannot acquire the policy of the provider service at URI {0} using a WS-MetadataExchange GetMetatadata request because the provider does not support the WS-MetadataExchange 1.1 GetMetadata action.
Explanation The client is configured to use the policy of the provider service specified in the message using a WS-MetadataExchange GetMetadata request, but the provider endpoint does not support this request. Action Ensure that the provider service is available and that it supports WS-MetadataExchange v1.1. If the provider does not support WS-MetadataExchange, an alternative is to configure the client to acquire the provider policy using an HTTP GET request.
CWPOL0004E: The client cannot establish a policy to invoke the provider service at URI {0} because it does not support the format of the metadata response to the WS-MetadataExchange request {1}.
Explanation The client is configured to use the policy of the provider service specified in the message using a WS-MetadataExchange GetMetadata request, with the WSDL inlined in the response itself. The response that the client received is not in the expected format. Action Ensure that the provider service returns its metadata inlined in the GetMetadata response. If this is not possible, an alternative is to configure the client to acquire the provider policy using an HTTP GET request.
CWPOL0005E: The client cannot recognize the format of the WSDL of the provider service at URI {0} that it has acquired to establish the provider policy.
Explanation The client has successfully acquired the WSDL of the service provider. The WSDL file might not be valid, or might be in WSDL 1.0 format. Action Check that the WSDL of the service provider is valid and in WSDL 1.1 format.
CWPOL0006E: The WSDL of the provider service at URI {0} that the client has acquired to establish the provider policy is not valid for the client service. The client was attempting to resolve the WSDL elements in the WSDL of the provider for service {1}, port {2}, operation {3}.
Explanation The client has successfully acquired the WSDL of the service provider. The received WSDL is not valid for the client service because it does not correspond to the structure (operation, service, ports) that the client expects. Action Inspect the WSDL of the provider service. If the WSDL is incorrect then contact the administrator of the provider service. If the WSDL for the provider is correct then the JAX-WS client application must be regenerated to match the provider service, reinstalled and reconfigured.
CWPOL0007I: There is no policy information in the WSDL of the provider service at URI {0} that the client has acquired to establish the provider policy.
Explanation The client has successfully acquired the WSDL of the service provider, but there is no policy information in that WSDL. The client assumes that there is no provider policy to apply to the client service. Action If the client must acquire policy information from the WSDL of the provider service, ensure that the provider service is configured to publish policy configuration in its WSDL.
CWPOL0008E: The WSDL of the provider service at URI {0} that the client has acquired to establish the provider policy contains a target namespace that does not match the namespace that the client was expecting. The namespace configured for the client service is {1}. The WSDL of the provider contains the target namespace {2}.
Explanation The client has successfully acquired the WSDL of the service provider. The received WSDL is not valid for the client service because it does not match the namespace that the client expects. Action The JAX-WS client application must be regenerated with the correct namespace for the provider service, reinstalled and reconfigured.
CWPOL0010E: The policy set {1} to secure the WS-MetadataExchange GetMetatadata request does not exist. The client cannot acquire the policy of the provider service at URI {0}.
Explanation The client is configured to acquire the policy of the provider service using a WS-MetadataExchange GetMetadata request with message-level security, but the policy set specified to secure the request does not exist. Action Reconfigure the client and specify a valid policy set for the WS-Metadata request.
CWPOL0011E: The policy set binding {1} to secure the WS-MetadataExchange GetMetatadata request does not exist. The client cannot acquire the policy of the provider service at URI {0}.
Explanation The client is configured to acquire the policy of the provider service using a WS-MetadataExchange GetMetadata request with message-level security, but the policy set binding specified to secure the request does not exist. Action Reconfigure the client and specify a valid policy set binding for the WS-Metadata request.
CWPOL0012E: Either the policy set {1} or the policy set binding {2} to secure the WS-MetadataExchange GetMetatadata request is not valid. The client cannot acquire the policy of the provider service at URI {0}.
Explanation The client is configured to acquire the policy of the provider service using a WS-MetadataExchange GetMetadata request with message-level security, but either the policy set or the binding specified to secure the request is not valid. Action Reconfigure the client and specify a valid policy set and binding for the WS-Metadata request.
CWPOL0013I: The policy set to secure the WS-MetadataExchange request {0} to acquire the policy of the provider service at URI {0} does not contain any security policy.
Explanation The client is configured to acquire the policy of the provider service using a WS-MetadataExchange GetMetadata request with message-level security, but the policy set specified to secure the request does not contain any security policy. Action If you require message-level security for the WS-MetadataExchange request, reconfigure the client and specify a policy set that contains security policy for the WS-MetadataExchange request.
CWPOL0030E: The client cannot establish how policy is configured for the service {0} because the configuration file at location {1} is not valid.
Explanation The client cannot read the configuration file that defines how policy is configured. Usually, the application server administration or Rational Application Development tools generate this file automatically. Action If the configuration file was edited directly, delete the file, use the administrative console or command line interfaces to configure the policy settings, then retry the application. If the problem is not resolved, or if the configuration file was not edited directly, see the problem determination information on the WAS Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
CWPOL0040E: The client cannot establish how policy is configured for the service {0} because while processing the WSDL document attached to the service the following exception occurred {1}.
Explanation An error occurred while processing the WSDL document attached to the JAX-WS service. Action Inspect the WSDL attached to the service. If the WSDL is incorrect then contact the administrator of the service.
CWPOL0100E: The client cannot calculate an effective policy using the policy of the service provider at URI {0} because the policy in the WSDL of the provider at attachment {1} is not valid.
Explanation The client is configured to use the policy of the provider service specified in the message. The client has successfully acquired the WSDL of the provider, but the syntax of the policy in the WSDL does not conform to the WS-Policy specification. Action If the application is programmed to refresh the provider policy, the refresh might resolve the problem. Alternatively, restart the client to refresh the provider policy that the client holds. If this does not resolve the problem, either configure the client so that it does not use the provider policy, or contact the administrator of the provider policy service to correct the policy in the WSDL of the provider.
CWPOL0101E: The client cannot calculate an effective policy using the policy of the service provider at URI {0} because the policy reference {1} in the provider WSDL at attachment {2} cannot be resolved.
Explanation The client is configured to use the policy of the provider service specified in the message. The client has successfully acquired the WSDL of the provider, but the WSDL contains a policy reference that the run time cannot resolve. Action If the application is programmed to refresh the provider policy, the refresh might resolve the problem. Alternatively, restart the client to refresh the provider policy that the client holds. If this does not resolve the problem, either configure the client so that it does not use the provider policy, or contact the administrator of the provider policy service to correct the policy in the WSDL of the provider so that the policy does not contain the policy reference.
CWPOL0103E: The client cannot calculate an effective policy using the policy of the service provider at URI {0} because the client run time cannot resolve one or more of the WSDL parts that were acquired from the WSDL of the service provider.
Explanation The client is configured to use the policy of the provider service specified in the message. The client run time cannot resolve all the imported parts of the WSDL of the provider. Action If the application is programmed to refresh the provider policy, the refresh might resolve the problem. Alternatively, restart the client to refresh the provider policy that the client holds. If this does not resolve the problem, either configure the client so that it does not use the provider policy, or contact the administrator of the provider policy service to correct the policy in the WSDL of the provider.
CWPOL0104E: The client cannot calculate an effective policy using the policy of the service provider at URI {0}.The client has acquired the following WSDL from the service provider {1}. The client cannot recognize the following assertions in the WSDL of the service provider {2}.
Explanation The client is configured to use the policy of the provider service specified in the message. The client has successfully acquired the WSDL of the provider, but the client cannot support all of the policy assertions in that WSDL. Action If the application is programmed to refresh the provider policy, the refresh might resolve the problem. Alternatively, restart the client to refresh the provider policy that the client holds. If this does not resolve the problem, consider whether the requirements of the provider side policy can be changed. If this is not possible, the client cannot communicate with the provider.
CWPOL0105E: The client cannot calculate an effective policy using the policy of the service provider at URI {0}. The client has acquired the following WSDL from the service provider {1}. The client cannot recognize the following assertions in the WSDL of the service provider {2}. The service provider cannot recognize the following assertions from the client.policy set {3}.
Explanation The client is configured to use the client.policy set and the policy of the provider service specified in the message. The client has successfully acquired the WSDL of the provider, but the client cannot support all of the policy assertions in that WSDL, and the provider cannot support all of the policy assertions from the client policy set. Action If the application is programmed to refresh the provider policy, the refresh might resolve the problem. Alternatively, restart the client to refresh the provider policy that the client holds. If this does not resolve the problem, consider whether the requirements of the provider side policy and the client.policy set can be changed. If this is not possible, the client cannot communicate with the provider.
CWPOL0106E: The client cannot calculate an effective policy using the policy of the service provider at URI {0} because the WSDL at attachment {1} contains policy specified at a version of the WS-Policy specification that the application server does not support. The namespace of the policy that is not supported is {2}.
Explanation The client is configured to use the policy of the provider service specified in the message. The client has successfully acquired the WSDL of the provider, but the namespace of the policy in the WSDL does not match the namespace that the application server supports. Action If the application is programmed to refresh the provider policy, the refresh might resolve the problem. Alternatively, restart the client to refresh the provider policy that the client holds. If this does not resolve the problem, contact the administrator of the provider service to ensure that the policy in the WSDL of the provider is at the correct version.
CWPOL0107E: The client cannot calculate an effective policy using the policy of the service provider at URI {0} because the WSDL that the client acquired from the service provider does not contain any policy assertions, and the run time cannot process the policy that is configured for the client.
Explanation The client has successfully acquired the WSDL of the provider, but that WSDL does not contain any WS-Policy policy assertions. The client run time has tried to use the client.policy set, but it cannot process this policy. Action If the policy set file was edited directly, delete the file, use the administrative console or command line interfaces to configure the policy settings, then retry the application. If the problem is not resolved, or if the policy set file was not edited directly, see the problem determination information on the WAS Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
CWPOL0108E: The client cannot calculate an effective policy for the request because it is unable to deduce a single policy that is applicable for all operations of the target service.
Explanation The client is configured to acquire its policy dynamically from the provider using ws-policy exchange. The client has successfully acquired the WSDL of the provider, but that WSDL specifies different effective policies for one or more operations. The client runtime cannot establish the correct policy to use for the request because the runtime is unable to determine the operation name of the request at runtime. This is likely to be because the client is a JAX-WS DII client. Action The provider policy must be the same for each of its operations of the service. If the application is programmed to refresh the provider policy, the refresh might resolve the problem. Alternatively, restart the client to refresh the provider policy that the client has obtained. If this does not resolve the problem, consider whether the requirements of the provider side policy can be changed so that the policy is the same for all the operations of the service. If this is not possible, the client will not be able to establish an effective policy with the provider using dynamic ws-policy exchange so the policy of the client will need to be configured statically.
CWPOL0200E: The client cannot calculate an effective policy using the policy of the service provider at URI {0} because an aspect of the client.policy configuration could not be transformed to WS-Policy standard format.
Explanation The client cannot calculate an effective policy using the policies of the client and the provider because there is a problem transforming the client.policy set. Action Examine the accompanying error messages to resolve the problem.
CWPOL0300E: The client cannot calculate an effective policy using the policy of the service provider at URI {0} because there is not enough binding information for the specified policy established for the interaction.
Explanation The client cannot calculate an effective policy using the policy of the service provider because there is a problem with the client binding information. Action Examine the accompanying error messages to resolve the problem.
CWPOL0301E: The client cannot establish the policy associated with the client because there is a problem reading the policy set {0}.
Explanation The client cannot establish the policy associated with the client because there is a problem with the client binding information. Action Examine the accompanying error messages to resolve the problem.
CWPOL1010E: The policy set {0} to secure WS-MetadataExchange GetMetadata requests targeted at service URI {1} does not exist.
Explanation The service provider specified in the message is configured to accept WS-MetadataExchange GetMetadata requests with message-level security from clients targeted at that service, but the policy set specified to secure these requests does not exist. Action Reconfigure the service provider and specify a valid policy set for the WS-MetadataExchange request.
CWPOL1011E: The policy set binding {0} to secure WS-MetadataExchange GetMetadata requests targeted at service URI {1} does not exist.
Explanation The service provider specified in the message is configured to accept WS-MetadataExchange GetMetadata requests with message-level security from clients targeted at that service, but the policy set binding specified to secure these requests does not exist. Action Reconfigure the service provider and specify a valid policy set binding for the WS-MetadataExchange request.
CWPOL1012E: Either the policy set {0} or the binding {1} to secure WS-MetadataExchange GetMetadata requests that are targeted at service URI {0} is not valid.
Explanation The service provider specified in the message is configured to accept WS-MetadataExchange GetMetadata requests with message-level security from clients targeted at that service, but the policy set or binding specified to secure these requests is not valid. Action Reconfigure the service provider and specify a valid policy set or binding for the WS-MetadataExchange request.
CWPOL1013I: The policy set {0} specified for securing WS-MetadataExchange GetMetadata requests targeted at service URI {1} does not contain security policy.
Explanation The service provider specified in the message is configured to accept WS-MetadataExchange GetMetadata requests with message-level security from clients targeted at that service, but the policy set or binding specified to secure these requests does not contain any security policy. Action If you require message-level security for the WS-MetadataExchange request, reconfigure the service provider and specify a policy set that contains security policy for the WS-MetadataExchange request.
CWPOL1030E: The service provider cannot establish how policy is shared for the service {0} because the configuration file at location {1} is not valid.
Explanation The service provider cannot read the configuration file that defines how policy is shared. Usually, the application server administration or Rational Application Development tools generate this file automatically. Action If the configuration file was edited directly, delete the file, use the administrative console or command line interfaces to configure the policy settings, then retry the application. If the problem is not resolved, or if the configuration file was not edited directly, see the problem determination information on the WAS Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
CWPOL1031I: The application server cannot publish the WSDL of the provider service {0}.
Explanation The policy of the provider service is not expressed in WSDL that complies with the WS-PolicyAttachments specification. It is possible to configure policy in a policy set that cannot be published using WS-Policy policy attachments in WSDL. Action Refer to the documentation for the application server.
CWPOL1200E: The policy configuration of the provider service {0} cannot be published because an aspect {1} of the provider policy configuration could not be transformed to WS-Policy standard format.
Explanation The service provider cannot share its policy because there is a problem transforming the provider policy configuration. Action Contact the administrator of the provider policy service to correct the policy in the WSDL of the provider.
CWPOL1201E: The policy configuration of the provider service {0} cannot be published because an aspect {1} of the provider policy configuration is attached to a scope point that is not in valid WS-Policy format.
Explanation The service provider cannot share its policy because there is a problem with the format of the policy configuration. Action Contact the administrator of the provider policy service to correct the policy in the WSDL of the provider.
CWPOL1250E: The WS-MetadataExchange GetMetadata request that is targeted at endpoint {0} is not supported because of an internal error.
Explanation There was an unexpected error when the application server processed a WS-MetadataExchange GetMetadata request. Action Examine the accompanying error messages to resolve the problem. If you cannot resolve the problem, see the problem determination information on the WAS Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
CWPOL1251E: The policy configuration in the WSDL for the service provider {0} cannot be published because of an internal error.
Explanation The service provider cannot share its policy because of an internal error. Action Examine the accompanying error messages to resolve the problem. If you cannot resolve the problem, see the problem determination information on the WAS Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
CWPOL7000E: No SSL configuration is available for the {0} endpoint. The SSL Alias that failed to resolve was {1}.
Explanation The system runtime was unable to resolve an effective SSL configuration for the specified endpoint. Action Make sure SSL configuration is correctly set for this endpoint. See the Information Center regarding the rules for securing communications using SSL.
CWPOL9000E: The class specified to acquire the policy from the provider cannot be loaded. The class name is {0}.
Explanation There was an unexpected error when the application server loaded the class that acquires policy from the provider. Action If the file was edited directly, delete the file, use the administrative console or command line interfaces to configure the policy settings, then retry the application. If the problem is not resolved, or if the file was not edited directly, see the problem determination information on the WAS Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
CWPOL9999E: The WS-Policy function that is requested for service {0} is not supported because of an internal error {1}.
Explanation There was an unexpected error when the application server processed WS-Policy information. Action See the problem determination information on the WAS Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.