Explanation | The service-ref element must contain a service-interface element. |
Action | Add the service-interface element and redeploy the application. |
Explanation | The service-ref element must contain a service-interface element. |
Action | Add the service-interface element and redeploy the application. |
Explanation | The service-ref element must contain a service-interface element. |
Action | Add the service-interface element and redeploy the application. |
Explanation | The service-interface element specifies a class that cannot be found or loaded. |
Action | Ensure the class is in the application class path. |
Explanation | The service-interface element specifies a class that cannot be found or loaded. |
Action | Ensure the class is in the application class path. |
Explanation | The service-interface element specifies a class that cannot be found or loaded. |
Action | Ensure the class is in the application class path. |
Explanation | The service-interface element must specify a subclass of the javax.xml.ws.Service class. |
Action | Specify a subclass of the javax.xml.ws.Service class in the service-interface element. |
Explanation | The service-interface element must specify a subclass of the javax.xml.ws.Service class. |
Action | Specify a subclass of the javax.xml.ws.Service class in the service-interface element. |
Explanation | The service-interface element must specify a subclass of the javax.xml.ws.Service class. |
Action | Specify a subclass of the javax.xml.ws.Service class in the service-interface element. |
Explanation | The service-interface class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-interface class. |
Explanation | The service-interface class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-interface class. |
Explanation | The service-interface class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-interface class. |
Explanation | The service-interface class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-interface class. |
Explanation | The service-interface class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-interface class. |
Explanation | The service-interface class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-interface class. |
Explanation | The service-ref-type class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-ref-type class. |
Explanation | The service-ref-type class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-ref-type class. |
Explanation | The service-ref-type class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-ref-type class. |
Explanation | The service-ref-type class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-ref-type class. |
Explanation | The service-ref-type class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-ref-type class. |
Explanation | The service-ref-type class declared in multiple places for the same service reference must be the same. |
Action | Correct the service reference to identify the same service-ref-type class. |
Explanation | If @WebServiceRef or @Resource annotation is found at the class-level, the type attribute must be identified. It may be specified within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify the missing type attribute. |
Explanation | If @WebServiceRef or @Resource annotation is found at the class-level, the type attribute must be identified. It may be specified within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify the missing type attribute. |
Explanation | If @WebServiceRef or @Resource annotation is found at the class-level, the type attribute must be identified. It may be specified within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify the missing type attribute. |
Explanation | The value attribute must be a subclass of the javax.xml.ws.Service class, unless the identified type attribute indicates a Service Endpoint Interface (SEI) injection. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor. |
Action | Specify a subclass of the javax.xml.ws.Service class. |
Explanation | The value attribute must be a subclass of the javax.xml.ws.Service class, unless the identified type attribute indicates a Service Endpoint Interface (SEI) injection. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor. |
Action | Specify a subclass of the javax.xml.ws.Service class. |
Explanation | The value attribute must be a subclass of the javax.xml.ws.Service class, unless the identified type attribute indicates a Service Endpoint Interface (SEI) injection. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor. |
Action | Specify a subclass of the javax.xml.ws.Service class. |
Explanation | If the annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the type and value attributes must be the same class. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor, and specify the type attribute within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify the same class for the value and type attributes. |
Explanation | If the annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the type and value attributes must be the same class. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor, and specify the type attribute within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify the same class for the value and type attributes. |
Explanation | If the annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the type and value attributes must be the same class. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor, and specify the type attribute within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify the same class for the value and type attributes. |
Explanation | If the class member type is Object, the type attribute must be specified and cannot be Object. You can specify the class member type within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify a type attribute other than Object. |
Explanation | If the class member type is Object, the type attribute must be specified and cannot be Object. You can specify the class member type within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify a type attribute other than Object. |
Explanation | If the class member type is Object, the type attribute must be specified and cannot be Object. You can specify the class member type within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify a type attribute other than Object. |
Explanation | The type attribute must be compatible with the class member type. You can specify the type attribute within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify an appropriate type attribute that is compatible with the class member type. |
Explanation | The type attribute must be compatible with the class member type. You can specify the type attribute within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify an appropriate type attribute that is compatible with the class member type. |
Explanation | The type attribute must be compatible with the class member type. You can specify the type attribute within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify an appropriate type attribute that is compatible with the class member type. |
Explanation | The value attribute must be a subclass of the javax.xml.ws.Service class, unless the identified type attribute indicates a Service Endpoint Interface (SEI) injection. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor. |
Action | Specify a subclass of javax.xml.ws.Service. |
Explanation | The value attribute must be a subclass of the javax.xml.ws.Service class, unless the identified type attribute indicates a Service Endpoint Interface (SEI) injection. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor. |
Action | Specify a subclass of javax.xml.ws.Service. |
Explanation | The value attribute must be a subclass of the javax.xml.ws.Service class, unless the identified type attribute indicates a Service Endpoint Interface (SEI) injection. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor. |
Action | Specify a subclass of javax.xml.ws.Service. |
Explanation | If the annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the type and value attributes must be the same class. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor, and specify the type attribute within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify the same class for the value and type attributes. |
Explanation | If the annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the type and value attributes must be the same class. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor, and specify the type attribute within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify the same class for the value and type attributes. |
Explanation | If the annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the type and value attributes must be the same class. You can specify the value attribute within the annotation or by the service-interface element in the deployment descriptor, and specify the type attribute within the @WebServiceRef annotation or by the service-ref-type element in the deployment descriptor. |
Action | Specify the same class for the value and type attributes. |
Explanation | If the lookup attribute of the @WebServiceRef annotation is specified, then no other attributes are allowed. |
Action | Remove the lookup attribute or the other attributes. |
Explanation | If the lookup attribute of the @WebServiceRef annotation is specified, then no other attributes are allowed. |
Action | Remove the lookup attribute or the other attributes. |
Explanation | If the lookup attribute of the @WebServiceRef annotation is specified, then no other attributes are allowed. |
Action | Remove the lookup attribute or the other attributes. |
Explanation | If a @WebServiceRef annotation is found at the class level, the name and type attributes must be specified. |
Action | Specify the missing name or type attribute. |
Explanation | If a @WebServiceRef annotation is found at the class level, the name and type attributes must be specified. |
Action | Specify the missing name or type attribute. |
Explanation | If a @WebServiceRef annotation is found at the class level, the name and type attributes must be specified. |
Action | Specify the missing name or type attribute. |
Explanation | The value attribute of the @WebServiceRef annotation must specify a subclass of the javax.xml.ws.Service class, unless the type attribute indicates a Service Endpoint Interface (SEI) injection. |
Action | Specify a subclass of the javax.xml.ws.Service class for the value attribute. |
Explanation | The value attribute of the @WebServiceRef annotation must specify a subclass of the javax.xml.ws.Service class, unless the type attribute indicates a Service Endpoint Interface (SEI) injection. |
Action | Specify a subclass of the javax.xml.ws.Service class for the value attribute. |
Explanation | The value attribute of the @WebServiceRef annotation must specify a subclass of the javax.xml.ws.Service class, unless the type attribute indicates a Service Endpoint Interface (SEI) injection. |
Action | Specify a subclass of the javax.xml.ws.Service class for the value attribute. |
Explanation | If the @WebServiceRef annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the class specified by the type and value attributes must be the same. |
Action | Specify the same class for the value and type attributes. |
Explanation | If the @WebServiceRef annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the class specified by the type and value attributes must be the same. |
Action | Specify the same class for the value and type attributes. |
Explanation | If the @WebServiceRef annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the class specified by the type and value attributes must be the same. |
Action | Specify the same class for the value and type attributes. |
Explanation | For JAX-WS service references, if the @WebServiceRef annotation is specified on a method, the method name must follow the standard JavaBeans convention, such as setHelloWorld or getHelloWorld. |
Action | Ensure the method name follows the standard JavaBeans conventions. |
Explanation | For JAX-WS service references, if the @WebServiceRef annotation is specified on a method, the method name must follow the standard JavaBeans convention, such as setHelloWorld or getHelloWorld. |
Action | Ensure the method name follows the standard JavaBeans conventions. |
Explanation | For JAX-WS service references, if the @WebServiceRef annotation is specified on a method, the method name must follow the standard JavaBeans convention, such as setHelloWorld or getHelloWorld. |
Action | Ensure the method name follows the standard JavaBeans conventions. |
Explanation | If the class member type is Object, the type attribute of the @WebServiceRef annotation must be specified and cannot be Object. |
Action | Specify a type attribute other than Object. |
Explanation | If the class member type is Object, the type attribute of the @WebServiceRef annotation must be specified and cannot be Object. |
Action | Specify a type attribute other than Object. |
Explanation | If the class member type is Object, the type attribute of the @WebServiceRef annotation must be specified and cannot be Object. |
Action | Specify a type attribute other than Object. |
Explanation | The type attribute must be compatible with the class member type. |
Action | Ensure that the type attribute is compatible with the class member type. |
Explanation | The type attribute must be compatible with the class member type. |
Action | Ensure that the type attribute is compatible with the class member type. |
Explanation | The type attribute must be compatible with the class member type. |
Action | Ensure that the type attribute is compatible with the class member type. |
Explanation | The value attribute of the @WebServiceRef annotation must specify a subclass of the javax.xml.ws.Service class, unless the type attribute indicates a Service Endpoint Interface (SEI) injection. |
Action | Specify a subclass of the javax.xml.ws.Service class for the value attribute. |
Explanation | The value attribute of the @WebServiceRef annotation must specify a subclass of the javax.xml.ws.Service class, unless the type attribute indicates a Service Endpoint Interface (SEI) injection. |
Action | Specify a subclass of the javax.xml.ws.Service class for the value attribute. |
Explanation | The value attribute of the @WebServiceRef annotation must specify a subclass of the javax.xml.ws.Service class, unless the type attribute indicates a Service Endpoint Interface (SEI) injection. |
Action | Specify a subclass of the javax.xml.ws.Service class for the value attribute. |
Explanation | If the @WebServiceRef annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the class specified by the type and value attributes must be the same. |
Action | Specify the same class for the value and type attributes. |
Explanation | If the @WebServiceRef annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the class specified by the type and value attributes must be the same. |
Action | Specify the same class for the value and type attributes. |
Explanation | If the @WebServiceRef annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the class specified by the type and value attributes must be the same. |
Action | Specify the same class for the value and type attributes. |
Explanation | The handler chain definition file cannot be found from the file attribute of handlerChain annotation. |
Action | Specify the path of an existing handler chain definition file. The path can be an absolute file path or relative to the class annotated with the handlerChain annotation. |
Explanation | The handler chain definition file cannot be found from the file attribute of handlerChain annotation. |
Action | Specify the path of an existing handler chain definition file. The path can be an absolute file path or relative to the class annotated with the handlerChain annotation. |
Explanation | The handler chain definition file cannot be found from the file attribute of handlerChain annotation. |
Action | Specify the path of an existing handler chain definition file. The path can be an absolute file path or relative to the class annotated with the handlerChain annotation. |
Explanation | The naming space of the root element is not equal to "http://java.sun.com/xml/ns/javaee" or the local name of the root element is not equal to "handler-chain". |
Action | Modify the naming space of the root element to be either "http://java.sun.com/xml/ns/javaee" or the local name of the root element to "handler-chain", then try again. |
Explanation | The naming space of the root element is not equal to "http://java.sun.com/xml/ns/javaee" or the local name of the root element is not equal to "handler-chain". |
Action | Modify the naming space of the root element to be either "http://java.sun.com/xml/ns/javaee" or the local name of the root element to "handler-chain", then try again. |
Explanation | The naming space of the root element is not equal to "http://java.sun.com/xml/ns/javaee" or the local name of the root element is not equal to "handler-chain". |
Action | Modify the naming space of the root element to be either "http://java.sun.com/xml/ns/javaee" or the local name of the root element to "handler-chain", then try again. |
Explanation | An unexpected exception was encountered when parsing the handler chain file. |
Action | Verify that the format of the handler file is correct and check the ffdc log in the appropriate logs/ffdc directory of the server for more details. |
Explanation | An unexpected exception was encountered when parsing the handler chain file. |
Action | Verify that the format of the handler file is correct and check the ffdc log in the appropriate logs/ffdc directory of the server for more details. |
Explanation | An unexpected exception was encountered when parsing the handler chain file. |
Action | Verify that the format of the handler file is correct and check the ffdc log in the appropriate logs/ffdc directory of the server for more details. |
Explanation | A file property is required in the handlerChain annotation. |
Action | Specify the appropriate file name in the handlerChain annotation. |
Explanation | A file property is required in the handlerChain annotation. |
Action | Specify the appropriate file name in the handlerChain annotation. |
Explanation | A file property is required in the handlerChain annotation. |
Action | Specify the appropriate file name in the handlerChain annotation. |
Explanation | An IOException occurred when loading the catalog file. |
Action | Ensure that the JAX-WS catalog file exists and its syntax conforms to the XML Catalog specification. |
Explanation | An IOException occurred when loading the catalog file. |
Action | Ensure that the JAX-WS catalog file exists and its syntax conforms to the XML Catalog specification. |
Explanation | An IOException occurred when loading the catalog file. |
Action | Ensure that the JAX-WS catalog file exists and its syntax conforms to the XML Catalog specification. |
Explanation | The web service does not contain a wsdlLocation or a SOAP/1.1 annotation. |
Action | Specify either a wsdlLocation or a SOAP/1.1 annotation to the web service. |
Explanation | The web service does not contain a wsdlLocation or a SOAP/1.1 annotation. |
Action | Specify either a wsdlLocation or a SOAP/1.1 annotation to the web service. |
Explanation | The web service does not contain a wsdlLocation or a SOAP/1.1 annotation. |
Action | Specify either a wsdlLocation or a SOAP/1.1 annotation to the web service. |
Explanation | An IOException occurred when writing the full WSDL definition to the stream. |
Action | Specify either a wsdlLocation or a SOAP/1.1 annotation to the web service. |
Explanation | An IOException occurred when writing the full WSDL definition to the stream. |
Action | Specify either a wsdlLocation or a SOAP/1.1 annotation to the web service. |
Explanation | An IOException occurred when writing the full WSDL definition to the stream. |
Action | Specify either a wsdlLocation or a SOAP/1.1 annotation to the web service. |
Explanation | The web service does not contain a wsdlLocation or a SOAP/1.1 annotation. |
Action | Specify a wsdlLocation or a SOAP/1.1 annotation to the web service. |
Explanation | The web service does not contain a wsdlLocation or a SOAP/1.1 annotation. |
Action | Specify a wsdlLocation or a SOAP/1.1 annotation to the web service. |
Explanation | The web service does not contain a wsdlLocation or a SOAP/1.1 annotation. |
Action | Specify a wsdlLocation or a SOAP/1.1 annotation to the web service. |
Explanation | Cannot create or initialize the handler. |
Action | Make sure that the handler class is in the class path of the application or the handler class provides an empty constructor. |
Explanation | Cannot create or initialize the handler. |
Action | Make sure that the handler class is in the class path of the application or the handler class provides an empty constructor. |
Explanation | Cannot create or initialize the handler. |
Action | Make sure that the handler class is in the class path of the application or the handler class provides an empty constructor. |
Explanation | The return type of the preDestory method must be void and the resources that are used by the the handler must be released. |
Action | Make sure that the return type of the preDestory method is void and all the resources that are used by the handler class are released. Check the log file in server_name/logs/ffdc directory for more details. |
Explanation | The return type of the preDestory method must be void and the resources that are used by the the handler must be released. |
Action | Make sure that the return type of the preDestory method is void and all the resources that are used by the handler class are released. Check the log file in server_name/logs/ffdc directory for more details. |
Explanation | The return type of the preDestory method must be void and the resources that are used by the the handler must be released. |
Action | Make sure that the return type of the preDestory method is void and all the resources that are used by the handler class are released. Check the log file in server_name/logs/ffdc directory for more details. |
Explanation | The service class was not found in the class path of the application. |
Action | Ensure that the service class is in the class path of the application. |
Explanation | The service class was not found in the class path of the application. |
Action | Ensure that the service class is in the class path of the application. |
Explanation | The service class was not found in the class path of the application. |
Action | Ensure that the service class is in the class path of the application. |
Explanation | It is required to use relative URL for WSDL location, which will not force the JAX-WS implementation to retrieve remote locations. |
Action | Update the WSDL location with relative URL via annotations or deployment plans. |
Explanation | It is required to use relative URL for WSDL location, which will not force the JAX-WS implementation to retrieve remote locations. |
Action | Update the WSDL location with relative URL via annotations or deployment plans. |
Explanation | It is required to use relative URL for WSDL location, which will not force the JAX-WS implementation to retrieve remote locations. |
Action | Update the WSDL location with relative URL via annotations or deployment plans. |
Explanation | The WSDL file specified for the implementation class cannot be found. |
Action | Specify an existing WSDL file to the web service. |
Explanation | The WSDL file specified for the implementation class cannot be found. |
Action | Specify an existing WSDL file to the web service. |
Explanation | The WSDL file specified for the implementation class cannot be found. |
Action | Specify an existing WSDL file to the web service. |
Explanation | If the binding type is specified using BindingType annotation or from deployment descriptor, its value must match the one in the WSDL document. |
Action | Update the value of the binding type to match the one in the WSDL document. |
Explanation | If the binding type is specified using BindingType annotation or from deployment descriptor, its value must match the one in the WSDL document. |
Action | Update the value of the binding type to match the one in the WSDL document. |
Explanation | If the binding type is specified using BindingType annotation or from deployment descriptor, its value must match the one in the WSDL document. |
Action | Update the value of the binding type to match the one in the WSDL document. |
Explanation | The required operation is not allowed to be performed. |
Action | Do not run unsupported operation. |
Explanation | The required operation is not allowed to be performed. |
Action | Do not run unsupported operation. |
Explanation | The required operation is not allowed to be performed. |
Action | Do not run unsupported operation. |
Explanation | The Jackson provider is not configured correctly. |
Action | Make sure the Jackson provider is configured correctly. If the error persists, check the FFDC log in the appropriate logs/ffdc directory of the server for more details. |
Explanation | The authorization token type specified in the server configuration is invalid. |
Action | Specify a valid authorization token type. |
Explanation | The WS-Security policy loader could not be registered with the CXF framework during server startup. Because of the error, the WS-Security runtime will not be invoked for any SOAP message and WS-Security constraints will not be added. |
Action | Address the error described in the message. |
Explanation | The wsSecurity-1.1 feature is enabled but the WS-Security component cannot find the wsSecurityClient element in server.xml. |
Action | If WS-Security constraints are required for a client web service application, add the required wsSecurityClient configuration element to server.xml. |
Explanation | The wsSecurity-1.1 feature is enabled but the WS-Security component cannot find the wsSecurityProvider element in server.xml. |
Action | If WS-Security constraints are required for a provider web service application, add the required wsSecurityProvider configuration element to server.xml. |
Explanation | The name specified for the callerToken element in the wsSecurityProvider configuration in the server.xml is not valid. |
Action | Check the server.xml file to make sure that a supported value is specified for the callerToken element. The valid values are displayed in the error message. |
Explanation | The callerToken in server.xml is set to UsernameToken and the Security header in the inbound SOAP message contains more than one UsernameToken. Because of this, the WS-Security runtime cannot determine which UsernameToken to use for the caller token. |
Action | Do one of the following: 1) Change the client configuration to send only one UsernameToken 2) Remove the callerToken configuration in server.xml |
Explanation | The callerToken configured in the server.xml is not present in the SOAP Security header. |
Action | Do one of the following: 1) Change the client configuration to send the correct caller token 2) Remove the callerToken configuration in the server.xml |
Explanation | A security subject for the caller token retrieved from the SOAP Security header could not be created. The reason for the error is described in the message. |
Action | Address the error described in the message. |
Explanation | The callerToken in the server.xml is set to X509Token, endorsingSupportingToken is set to true (the default), and there is more than one EndorsingSupportingTokens in the inbound SOAP Security header. Since a single caller token must exist in the message for a caller token to be successfully selected, having multiple EndorsingSupportingTokens is not allowed. |
Action | Do one of the following: 1) Change the policy so that only one endorsingSupportingToken will be included in the message, 2) Remove the callerToken configuration in the server.xml, 3) Set endorsingSupportingToken to false in the callerToken configuration in server.xml |
Explanation | The callerToken in the server.xml is set to X509Token, endorsingSupportingToken is set to false, and there is more than one Asymmetric signature token in the inbound SOAP Security header. Since a single caller token must exist in the message for a caller token to be successfully selected, having multiple Asymmetric signature tokens is not allowed. |
Action | Do one of the following: 1) Change the policy so that only one Asymmetric signature token will be included in the message, 2) Remove the callerToken configuration in the server.xml |
Explanation | The NotBefore assertion within the SAML token specifies the time at which the token becomes valid; the token cannot be used before this time. To use this SAML token, the value of the NotBefore assertion must be an instant in the past. A possible reason for the error is that the receiver's clock is out of sync with the clock of the creator of the assertion. |
Action | Make sure the date and time on the IdP is synchronized with this SAML Web Single Sign-On (SSO) service provider, or increase the clock skew. |
Explanation | The NotOnOrAfter assertion within the SAML token specifies the time at which the token expires. The token must be used before this time. A possible reason for the error is that the receiver's clock is out of sync with the clock of the creator of the assertion. |
Action | Make sure the date and time on the IdP is synchronized with this SAML Web Single Sign-On (SSO) service provider, or increase the clock skew. |
Explanation | The IssueInstant assertion within the SAML token was too far in the past for this token to be used. A SAML token must be used within a configured time after being issued. A possible reason for the error is that the receiver's clock is out of sync with the clock of the creator of the assertion. |
Action | Make sure the date and time on the IdP is synchronized with this SAML Web Single Sign-On (SSO) service provider, or increase the clock skew. |
Explanation | The IssueInstant assertion within the SAML token was set to a time in the future and is therefore not yet considered valid. The IssueInstant value must be in the past in order for the SAML token to be valid. A possible reason for the error is that the receiver's clock is out of sync with the clock of the creator of the assertion. |
Action | Make sure the date and time on the IdP is synchronized with this SAML Web Single Sign-On (SSO) service provider, or increase the clock skew. |
Explanation | An exception occurred while parsing the SAML token. The token might have been malformed, or there was an internal error while attempting to parse the token string. |
Action | Check the server logs for more information about the error. |
Explanation | An exception occurred while extracting the SAML token from the subject. |
Action | Check the server logs for more information about the error. |
Explanation | An exception occurred while attempting to obtain information about the subject from the provided SAML token. |
Action | Check the server logs for more information about the error. |
Explanation | There was likely a problem obtaining subject or identity information while interacting with the user registry. |
Action | Check the server logs for more information about the error. Ensure that the subject information in the SAML token maps to the expected values in the configured user registry. |
Explanation | The password type in the UsernameToken did not match the required password type as defined in the WS-Security policy. These types must be identical; the web service client must assert the same password type that is defined in the WS-Security policy in order for validation to succeed. |
Action | Ensure that the web service client asserts the same password type that is defined in the WS-Security policy. |
Explanation | The password in the UsernameToken was neither hashed nor in plaintext and was therefore considered a custom password type. The configuration in the request data specifies that custom password types are not supported. |
Action | Ensure that the web service client uses a password type as defined in the UsernameToken profile, or configure the web service provider to accept custom password types. |
Explanation | The user name or password entries in the UsernameToken were either missing or empty. |
Action | Check that a user name and password are provided in the token. If a user name and password are not provided, obtain a new UsernameToken. |
Explanation | There was an error obtaining a reference to the user registry from the user registry service, or an exception occurred while checking the password for the given user. |
Action | Check the server logs for more information about the exception. Ensure that the provided user name and password are correct and correspond to an entry in the configured user registry. |
Explanation | The specified user could not be validated against the configured user registry. This is likely due to a user name or password mismatch. |
Action | Check the provided credentials to ensure that the user name and password match an entry in the configured user registry. |
Explanation | The password callback handler must return a non-null password for passwords of type PasswordDigest within a UsernameToken. |
Action | Ensure that the password callback handler returns a non-null and non-empty password for a valid user. |
Explanation | The SAML assertion is either missing the attribute or the caller configuration specified a wrong value for the mentioned identifier. |
Action | Do one of the following: 1)Make sure that the attribute exists in the SAML assertion. 2) Configure the callerToken to specify a different attribute as the identifier. |
Explanation | The SAML assertion is missing an element required by the WS-Security run time to complete the processing of the caller token. |
Action | Do one of the following: 1)Make sure that the required element exists in the SAML assertion. 2) Configure the callerToken to define a value for the element. |
Explanation | The UserCredentialResolver service provided by the user feature can not map the SAML Assertion properly and throws a UserIdentityException. |
Action | Make sure the UserCredentialResolver service is properly set up if the UserIdentityException is not expected. |
Explanation | The callerToken in the server.xml is set to SamlToken and the Security header in the inbound SOAP message contains more than one Saml Assertion. Because of this, the WS-Security runtime cannot determine which Saml Assertion to use for the caller token. |
Action | Do one of the following: 1) Change the client configuration to send only one Saml Assertion 2) Remove the callerToken configuration in the server.xml |
Explanation | A security subject for the caller token retrieved from the SOAP Security header could not be created. Make sure that the user specified in the message exists in the user registry. |
Action | Do one of the following: 1) Make sure that the user exists in the user registry in the server.xml. 2) Do not set the mapToUserRegistry attribute in the callerToken configuration. |
Explanation | At least one callback must be passed to the callback handler in order to process and return a SAML token. |
Action | There is no user action available for this case. |
Explanation | There was an error extracting the SAML token from the subject or a SAML element was not found in the current subject. |
Action | If you create the run-as subject, make sure that the SAML token is added to the subject. Otherwise ensure that your server configuration supports adding the SAML token to the subject by checking the includeTokenInSubject attribute in your SAML configuration. |
Explanation | The value of the <port-component-name> element must not be null or empty. |
Action | Ensure that the value of the <port-component-name> element is not null or empty. |
Explanation | The value of the <protocol-binding> element in the webservices.xml must be one of the following URLs ("http://schemas.xmlsoap.org/wsdl/soap/http","http://www.w3.org/2003/05/soap/bindings/HTTP/","http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true","http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true") or their alias ##SOAP11_HTTP,##SOAP11_HTTP.MTOM,##SOAP12_HTTP,##SOAP12_HTTP.MTOM,##XML_HTTP. |
Action | Use one of the following URLs ("http://schemas.xmlsoap.org/wsdl/soap/http","http://www.w3.org/2003/05/soap/bindings/HTTP/","http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true","http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true") or their alias ##SOAP11_HTTP,##SOAP11_HTTP.MTOM,##SOAP12_HTTP,##SOAP12_HTTP.MTOM,##XML_HTTP for the protocol binding. |
Explanation | The value of the <wsdl-service> element in the webservices.xml must be a qualified name. |
Action | Use a qualified name for the <wsdl-service> element in the webservices.xml. A qualified name should contain an XML name-space and a local-name. For example, the <wsdl-service> should be defined like <wsdl-service xmlns:pfx="http://com.ibm.example">pfx:ExampleWSDLService</wsdl-service> in the webservices.xml. |
Explanation | The value of the <wsdl-port> element in the webservices.xml must be a qualified name. |
Action | Use a qualified name for the <wsdl-port> element in webservices.xml. A qualified name should contain an XML name-space and a local-name. For example, the <wsdl-port> should be defined like <wsdl-port xmlns:pfx="http://com.ibm.example">pfx:ExampleWSDLPort</wsdl-port> in the webservices.xml. |
Explanation | If the namespace of the <wsdl-port> element is specified, it must match the namespace specified in the <wsdl-service> element. |
Action | Specify a namespace that matches the one specified in the <wsdl-service> element. |
Explanation | The value of the <service-endpoint-interface> element in the webservices.xml must be a fully qualified class name. |
Action | Use a fully qualified class name for the <service-endpoint-interface> element in the webservices.xml. The fully qualified class name should be something like <package_name>.<class_name>, for example, com.ibm.ws.example.MyService. |
Explanation | The value of the <mtom-threshold> element in the webservices.xml must be a non-negative integer. |
Action | Use a non-negative integer for the <mtom-threshold> element in the webservices.xml. |
Explanation | The value of the <enable-mtom> element in the webservices.xml must be a boolean value. |
Action | Set the value of the <enable-mtom> element to true or false. |
Explanation | The value of the <enabled> element defined in the <respect-binding> element must be a boolean value. |
Action | Set the value of the <enabled> element to true or false. |
Explanation | The value of the <enabled> or the <required> element defined in the <addressing> element must be a boolean value. |
Action | Set the value of the <enabled> or the <required> element to true or false. |
Explanation | The <handler-class> element and the <handler-name> element are required when a handler is set. |
Action | Set the <handler-class> element and the <handler-name> element to a valid handler. The value of the <handler-name> element must be a unique name in the same webservices.xml. The value of the <handler-class> element must be a fully qualified class name. The fully qualified class name should be something like <package_name>.<class_name>, for example, com.ibm.ws.example.MyHandler. |
Explanation | The url-pattern of the servlet-mapping must be an exact match pattern and must not contain an asterisk. |
Action | Make sure that url-pattern of servlet-mapping of the servlet is an exact match pattern. |
Explanation | The url-pattern of the servlet-mapping must be an exact match pattern and must not contain an asterisk. |
Action | Make sure that url-pattern of servlet-mapping of the servlet is an exact match pattern. |
Explanation | The specified handler class cannot be loaded. |
Action | Update the application to include the handler class. |
Explanation | The sslRef attribute specified in the ibm-ws-bnd.xml file cannot refer to the ssl element in the server.xml file, or the content of the referred ssl element is invalid. |
Action | Ensure that the value of the sslRef attribute matches the id of the ssl element in the server.xml file, or the content of the referred ssl element is correct. |
Explanation | Invalid configuration of keystore or truststore element in the server.xml file can result in the exception because the sslRef attribute specified in the ibm-ws-bnd.xml file refers to the SSL configurations in the server.xml file. |
Action | Ensure that the location and the password of the keystore or the truststore element are correctly specified in the server.xml file, and the certificate alias is valid in the ibm-ws-bnd.xml file. |
Explanation | The login-config element can only be configured in the web.xml file of the web application, and the login-config element defined in the ibm-ws-bnd.xml file is ignored. |
Action | Ensure that the login-config element is only configured in the web.xml file of your web application. |
Explanation | The ibm-ws-bnd.xml file only supports BASIC and CLIENT_CERT as auth-method type. |
Action | Ensure that the value of auth-method type defined in the ibm-ws-bnd.xml file is either BASIC or CLIENT_CERT. |
Explanation | If the target parameter is specified, existing applications can be re-generated without changing their behavior when the JAXB specification level supported by the Liberty Profile is updated. |
Action | Specify the JAXB specification level to which the generated code conforms. The valid value is 2.0, 2.1, or 2.2. |
Explanation | The type of the timeout value must be long or int. |
Action | Set the type of the value to long or int. |
Explanation | The type of the proxy server port value must be int. |
Action | Set the type of the value to int. |
Explanation | The value of the proxy server type must be HTTP or SOCKS. |
Action | Set the value to HTTP or SOCKS. |
Explanation | A valid reference id is required to generate an SSL socket factory. There is no SSL configuration with id {0} in the server.xml file. |
Action | Set a valid SSL reference id in the server.xml file. |
Explanation | There was an error extracting the SAML token from the subject or a SAML element was not found in the current subject. |
Action | If you create the run-as subject, make sure that the SAML token is added to the subject. Otherwise ensure that your server configuration supports adding the SAML token to the subject by checking the includeTokenInSubject attribute in your SAML configuration. |
Explanation | An exception occurred while invoking the PropagationHelper API to retrieve the SAML token from the subject. |
Action | Ensure that the server.xml has the samlWeb-2.0 feature specified. Also, check the server logs for additional information regarding the exception. |
Explanation | An exception occurred while getting the RunAsSubject. |
Action | Make sure the server is configured and started properly. |
Explanation | If the target parameter is specified, existing applications can be re-generated without changing their behavior when the JAX-WS specification level supported by the Liberty Profile is updated. |
Action | Specify the JAX-WS specification level to which the generated code conforms. The valid value is 2.0, 2.1, or 2.2. |
Explanation | Either an unsupported Java version is running, or the JAVA_HOME system variable is set to point to an older version of Java. |
Action | Upgrade the Java version to Java 7, or adjust the JAVA_HOME system variable to point to Java 7. |
Explanation | Liberty gets resource instance from JAXRS if it cannot get instance from CDI. |
Action | No action is required. |
Explanation | If the JAXRS-2.0 Resource scope does not match the CDI scope and the resource instance exists in CDI, Liberty gets the resource instance from CDI. Instance does not include CDI injection if it is from JAXRS. |
Action | No action is required. |
Explanation | Provider instance is Singleton only. Liberty gets provider instance from CDI if the CDI scope of provider is Dependent or ApplicationScoped. Instance does not include CDI injection if it is from JAXRS. |
Action | No action is required. |
Explanation | If the JAXRS-2.0 Resource scope does not match the EJB scope, and the resource instance exists in EJB, Liberty gets the resource instance from EJB. |
Action | No action is required. |
Explanation | Provider instance is Singleton only. Liberty gets provider instances from EJB if the EJB scope of provider is Dependent or ApplicationScoped. |
Action | No action is required. |
Explanation | The EJB class {0} does not have default constructor. Liberty gets the InstantiationException exception when it tries to instantiate the EJB instance. |
Action | No action is required. |
Explanation | The EJB class {0} can not be loaded. |
Action | Correct your application to fix the issue. |