WSSAPE0029 | Failed to initialize argus configuration due to the following: {0}. |
Explanation |
An argus configuration file is invalid or unavailable, or a WS_STACK_HOME variable is not set. |
Action |
Make sure that the WS_STACK_HOME environment variable is properly set. Check the path to the argus configuration file and make sure that the argus configuration file is valid and not empty. |
WSSAPE0030 | Unknown user: {0}. |
Explanation |
The user cannot be authenticated because the supplied username is not correct. |
Action |
Provide a valid username. |
WSSAPE0031 | Unknown password callback type: {0} |
Explanation |
Only UsernameToken authentication is supported. You use a different authentication mechanism. |
Action |
Provide a valid username and password. |
WSSAPE0032 | An argus username is not configured in the argus agents properties file. |
Explanation |
The entries in argus agents properties file must be initialized. The "wsstack.adminservice.user" property does not contain a valid value. |
Action |
Provide a valid, non-empty value for "wsstack.adminservice.user" property in the argus agents properties file. |
WSSARE0000 | Login failed. |
Explanation |
Authentication fails. Invalid or empty credentials provided. |
Action |
Provide valid, non-empty username and password. |
WSSARE0001 | The following Web service archive does not comply with the naming standards: {0}. The archive is not deployed. |
Explanation |
The artifact name and extension contain invalid characters or do not comply with the correct name format. |
Action |
Edit the current artifact to conform to the AAR standards. Rename the archive using a valid name. The '.aar' extension cannot contain capital letters. |
WSSARE0030 | A problem occurred while executing a Web service. The Web service name is ''{0}'' with request payload ''{1}''. |
Explanation |
There is a problem while executing the Web service. |
Action |
Make sure that the requested Web service is operational. |
WSSARI0027 | Version information. |
Explanation |
A version information label. |
Action |
None. |
WSSASE0000 | Cannot find library jar file ''{0}'' |
Explanation |
The message appears when Web Services Stack administration service is tyring to locate the axis2-kernel jar but the file does not exist or its location cannot be determined. |
Action |
Assert that the reported file exists and it is not locked by another process on the system. |
WSSASE0009 | Cannot find library directory ''{0}'' |
Explanation |
The message appears when Web Services stack administration service is trying to locate the library directory with the jar files used by the Web Services Stack runtime. |
Action |
Assert that the reported path exists and it is a valid directory. |
WSSCLE0001 | Deployment configuration file cannot be null. |
Explanation |
A valid deployment configuration file was not specified or an empty value for deployment configuration file was provided. |
Action |
Specify a valid deployment configuration file. |
WSSCLE0002 | [{0}] object cannot be null. |
Explanation |
Deployment configurator is not initialized correctly and returns null. |
Action |
You must initialize the deployment configurator with a valid, non-empty deployment configuration file or valid deployment configuration properties. |
WSSCLE0003 | The specified transport protocol [{0}] is not supported. |
Explanation |
The transport protocol defined in the DeploymentConfigurator is not supported. |
Action |
Set HTTP or HTTPS transport in the DeploymentConfigurator. |
WSSCLE0004 | Deployment configuration properties object cannot be null. |
Explanation |
Valid deployment configuration properties are not specified or empty values for deployment configuration properties are provided. |
Action |
Specify valid, non-empty deployment configuration properties. |
WSSCLE0005 | Problems while loading the deployment configuration from the file with the following location path: [{0}]. |
Explanation |
Deployment configuration cannot be loaded from the specified file. |
Action |
Check whether the provided configuration file is valid and whether its location path is correct. |
WSSCLE0006 | "Servlet context" configuration is not found. The needed "servlet context" configuration is not set into the deployment configuration file. |
Explanation |
The deployment configuration property that specifies the servlet context is not set into the deployment configuration file. |
Action |
Set the servlet deployment configuration property into the deployment configuration file. |
WSSCLE0007 | "Host name" configuration is not found. The needed "host name" configuration is not set into the deployment configuration file. |
Explanation |
The deployment configuration property hostname is not set into the deployment configuration file or the given value cannot be resolved. |
Action |
Set a valid, non-empty value for the hostname property into the deployment configuration file. |
WSSCLE0008 | Unknown "host name" configuration found. You can find the needed "host name" configuration into the deployment configuration file. |
Explanation |
The deployment configuration property hostname is set with a value that cannot be resolved. |
Action |
Set a valid, non-empty value for the hostname property into the deployment configuration file. |
WSSCLE0009 | Invalid "port number" configuration found. You can find the needed "port number" configuration into the deployment configuration file. |
Explanation |
In the deployment configuration property port is set an invalid value. |
Action |
Set a valid port property into the deployment configuration file. |
WSSCLE0010 | Service name [{0}] for undeployment is invalid. |
Explanation |
The Web service added for undeployment does not have a valid service name. |
Action |
Add a valid service name for the Web service that you want to undeploy. |
WSSCLE0011 | Archive data unit must not be "null". |
Explanation |
The archive file added for deployment is null or invalid. |
Action |
Add a valid archive file for deployment. |
WSSCLE0012 | Failed to parse the configured [{0}] with value [{1}]. The default value [{2}] will be used. |
Explanation |
The given value for maxConnectionsPerHost is invalid or cannot be processed. A default value will be used instead. |
Action |
Set a valid positive integer for the value of maxConnectionsPerHost. Otherwise, an alternative default value will be used. |
WSSCLE0013 | Failed to parse the configured [{0}] with value [{1}]. The default value [{2}] will be used. |
Explanation |
The given value for maxTotalConnections is invalid or cannot be processed. A default value will be used instead. |
Action |
Set a valid positive integer for the value of maxTotalConnections. Otherwise, an alternative default value will be used. |
WSSCLE0014 | There are no archives added for deployment. |
Explanation |
Web service archives are not added for deployment or undeployment. |
Action |
Add Web service archives for deployment or undeployment. |
WSSCLE0015 | An error is thrown during the retrieval of the deployment result. |
Explanation |
Deployment result cannot be retrieved because of an error while executing the remote operation. |
Action |
Check the connection to the server and the error log. |
WSSCLE0016 | An error is thrown during the retrieval of the deployment result. The cause of the error is: {0} |
Explanation |
Deployment result cannot be retrieved because of an error while executing the remote operation. |
Action |
Check the connection to the server and the error log. |
WSSCLE0017 | The URI given for deployment is invalid. The passed value is [{0}]. |
Explanation |
The given URI for deployment is empty or the given value cannot be parsed as a URI reference. |
Action |
Provide a valid, non-empty URI for deployment. |
WSSCLE0018 | The org.apache.commons.httpclient.HostConfiguration object passed is "null". |
Explanation |
The HostConfiguration is empty. |
Action |
Check that the properties set for the host have valid, non-empty values and check the connection. |
WSSCLE0019 | An error while deploying Web services occurs due to a problem while invoking the operation on the remote server . Reason: {0}. |
Explanation |
An error occurs during the deployment. The services cannot be deployed. |
Action |
Check the error log for details. |
WSSCLE0020 | An error while undeploying services occurs due to a problem while invoking the operation on the remote server. Reason: {0}. |
Explanation |
An error occurs during undeployment. The services cannot be undeployed. |
Action |
Check the error log for details. |
WSSCLE0021 | An error while listing the Web services occurs due to a problem while invoking the operation on the remote server. Reason: {0}. |
Explanation |
An error occurs while listing services. |
Action |
Check the error log for details. |
WSSCLE0022 | An error while listing properties occurs due to a problem while invoking the operation on the remote server. Reason: {0}. |
Explanation |
An error occurs while listing properties. |
Action |
Check the error log for details. |
WSSCLE0023 | The given keystore file {0} cannot be converted to a URL. |
Explanation |
The given value for the keystore file cannot be parsed. |
Action |
Provide a valid, non-empty value for the keystore file and check its location path. |
WSSCLE0024 | The given truststore file {0} cannot be converted to a URL. |
Explanation |
The given value for the truststore file cannot be parsed. |
Action |
Provide a valid, non-empty value for the truststore file and check its location path. |
WSSCLE0025 | The given proxy port with value [{0}] is invalid. |
Explanation |
The value provided for a proxy port is not in the correct format. |
Action |
Provide a valid proxy port. If you do not want to use a proxy port do not set a value to it. |
WSSCLE0030 | The WSDL definition cannot be null. |
Explanation |
You have not specified a WSDL definition. |
Action |
Specify a valid, non-empty WSDL definition. |
WSSCLE0031 | The WSDL URL cannot be null. |
Explanation |
You have not specified a WSDL URL or you have provided a null or empty value. |
Action |
Specify a valid, non-empty WSDL URL. |
WSSCLE0032 | The constructor is not found. |
Explanation |
You did not provide a valid constructor for the class. |
Action |
Check the parameters you used. One or more of them are not suitable for the class. Use one of the available constructors for instantiating the class. |
WSSCLE0033 | This action is not supported. |
Explanation |
You are trying to use functionality that is not yet implemented. |
Action |
This action is not supported. Contact Software AG Global Support. |
WSSCLE0034 | Service [{0}] is not found. |
Explanation |
The service with the specified name [{0}] is not available. |
Action |
Check the service name. |
WSSCLE0035 | Problem getting the WSDL, HTTP error code: {0}. |
Explanation |
The operation for getting the WSDL encounters a problem. |
Action |
Check the causes for the HTTP status error code. |
WSSCLE0036 | Cannot apply Web service client policy. |
Explanation |
Policy cannot be applied to the description hierarchy. |
Action |
Check and validate the configuration and the policy. |
WSSCLE0037 | Cannot locate the security configuration file ''{0}'' specified in the axis2 configuration under the key ''securityConfigFile''. |
Explanation |
The specified configuration security in the axis2 configuration file cannot be found. The properties cannot be loaded. |
Action |
If you want to load security properties from a custom security configuration file it must be placed in the proper place. The file is searched as defined in axis2 configuration under the key ''securityConfigFile''. Check the path and the file name. |
WSSCLE0038 | Cannot close security configuration file properly. |
Explanation |
An error occurs during close operation of the security configuration file. |
Action |
None. |
WSSCLE0039 | The WSDL file or WSDL definition cannot be found. |
Explanation |
In order to extract policies, either the WSDL location or the WSDL4J definition object must be valid. They are both missing or empty. |
Action |
Provide either a WSDL file or a valid WSDL definition. |
WSSCLE0040 | The class of the supplied callback must extend org.apache.axis2.client.async.Callback. |
Explanation |
The class of the supplied callback does not extend org.apache.axis2.client.async.Callback. It cannot be used. |
Action |
Provide a valid callback class. |
WSSCLE0041 | Failed to create a new client factory instance. |
Explanation |
Client factory instance cannot be created because the class cannot be found or instantiated. |
Action |
Check the configuration and the validity of the used constructor. |
WSSCLE0042 | Failed to create new client factory instance. |
Explanation |
The supplied factory class name argument does not resolve to a valid com.softwareag.wsstack.client.api.AbstractClientFactory implementation. Client factory instance cannot be created because the class name argument is not a com.softwareag.wsstack.client.api.AbstractClientFactory implementation. |
Action |
Give a fully quialified name of the factory implementation class that is going to be instantiated. |
WSSCLE0043 | Output stream cannot be null. |
Explanation |
The given output stream is not initialized or empty. |
Action |
Give a valid, non-empty output stream. |
WSSCLE0044 | Policy input stream cannot be null. |
Explanation |
The given policy input stream is not initialized or empty. |
Action |
Give a valid, non-empty policy input stream. |
WSSCLE0045 | Failed to close the WSDL input stream after reading. |
Explanation |
The close operation for the used WSDL input stream did not finish successfully. |
Action |
None. |
WSSCLE0046 | The provided content is too large to be buffered: {0} bytes. |
Explanation |
The content exceeds the maximum possible value that can be buffered. |
Action |
Contact Software AG Global Support. |
WSSCLE0047 | Cannot create DataObject for type {0}. |
Explanation |
The requested type {0} cannot be identified. |
Action |
The used data type is not supported. Use an alternative data type. |
WSSCLE0048 | Failed to create a wsstack client instance out of the following class: ''{0}''. |
Explanation |
A client instance cannot be created because the class cannot be found or instantiated. |
Action |
Check whether the name of the used class is correct. |
WSSCLE0049 | Failed to create a wsstack client instance. The class ''{0}'' is not a valid IWSBasicClient implementation. |
Explanation |
The defined class exists but its usage is incorrect. The class ''{0}'' cannot be used for instantiating a wsstack client because it is not a valid IWSBasicClient implementation. |
Action |
Define a valid implementation class. |
WSSCLE0050 | The services are not added for undeployment |
Explanation |
Web service archives are not added for undeployment. |
Action |
Add service archives for undeployment. |
WSSCLE0051 | The WS-Stack Java version is older than the Java version of the compiled archive ''{0}''. |
Explanation |
You compiled your archive with a newer Java version than the available in WS-Stack. The service cannot be deployed successfully. |
Action |
Compile the archive with an older Java version. You can check the supported Java version in the validation page of WS-Stack listed as java.version. |
WSSCLE0052 | There is a corrupted Java class file in the following archive: ''{0}''. |
Explanation |
One or more of the class files in the archive is corrupted or it is not a valid Java class file. |
Action |
Check the classes in your archive. Compile them with a supported Java version in WS-Stack and deploy the archive again. |
WSSCLE0053 | An error occurred while reading the archive ''{0}''; the archive is corrupted or empty. |
Explanation |
The archive that you want to deploy is not valid. It may be empty or cannot be read. |
Action |
Check and validate the content of archive ''{0}''. You may need to repack the content and deploy it again. |
WSSCLE0054 | An error occurred while manipulating the archive ''{0}''. The archive is locked or another Input/Output related problem has occurred. |
Explanation |
Other processes locked the archive and it cannot be processed or an Input/Output related problem has interrupted the execution of the command. |
Action |
Deploy the archive again. |
WSSCLE0056 | Cannot configure client factory thread pool. |
Explanation |
The error occurs when the WSStack client factory tries to configure a client instance to use a thread pool, and the client already has a thread pool set. |
Action |
Contact Software AG Global Support. |
WSSCLE0057 | The specified attachment lifecycle manager instance is not valid. |
Explanation |
The error occurs when the WSStack client factory configures a client instance to use an attachment lifecycle manager set by the user, and the specified lifecycle manager property is not a valid instance of org.apache.axiom.attachments.lifecycle.LifecycleManager. |
Action |
Specify a valid instance of ''org.apache.axiom.attachments.lifecycle.LifecycleManager'' under the client factory property key ''attachmentsLifecycleManager''. |
WSSCLE0058 | Cannot configure attachment lifecycle manager for a client instance. |
Explanation |
The error occurs when the Web Services Stack client factory configures a client instance to use a specific attachment lifecycle manager set by the user. Essentially, the error occurs when the attachment lifecycle parameter is locked. |
Action |
Contact Software AG Global Support. |
WSSCLE0059 | The supplier object (an instance of {0}) is not a proxy instance. |
Explanation |
The Web Services Stack client registry API provides a utility for retrieving the internal client configuration from a Web service proxy object. This error indicates that the tool is being used with a wrong proxy implementation (it is not a WSS compliant Web service client proxy). |
Action |
Modify your client implementation as the utility is used only with proxies created by the Web Services Stack registry API. |
WSSCLI0000 | Unable to locate the default security configuration file ''{0}''. |
Explanation |
The default security configuration file cannot be found and its properties are not loaded. |
Action |
If you want to load security properties from the default security configuration file, the file must be placed in the proper directory. The default security configuration file name is "wsclientsec.properties" and it must be either in the current working directory, or in "<REPOSITORY_DIRECTORY>/conf". |
WSSCLI0026 | An XMLStreamException thrown. |
Explanation |
The close operation for the used XMLStreamWriter did not finish successfully. |
Action |
None. |
WSSCLW0027 | Unable to locate the default security configuration file: ''{0}''. |
Explanation |
The default security configuration file cannot be found. Its properties are not loaded. |
Action |
If you want to load security properties from the default security configuration file you must put it in the proper place. The file is searched on the following location: ''{0}". |
WSSCLW0028 | The service policy is not set; cannot write service policy to the given stream. |
Explanation |
The service policy is not set. |
Action |
To associate a policy, use one of the setPolicy methods first. |
WSSCLW0029 | Overwriting an existing policy. |
Explanation |
This is an existing policy and it is going to be overwritten. |
Action |
Do not use this method if you expect different behavior. |
WSSCLW0055 | The parameters for max connections settings passed to configure the connection manager, associated with the HttpClient, caused a problem. |
Explanation |
The default parameters will be used for the non-standard ones. \n MAX_HOST_CONNECTIONS parameter passed is ''{0}''. \n MAX_TOTAL_CONNECTIONS parameter passed is ''{1}''. |
Action |
None. |
WSSCME0001 | Key value cannot be null or empty |
Explanation |
The error appears when you prepare configuration properties parser of a security module. This implementation is used only in private constructors and therefore the error appears only if a severe implementation fault occurs. |
Action |
The error indicates a severe fault in the Web Services Stack implementation. If the error occurs, report it to the software development team. |
WSSCME0002 | Rampart configuration element value cannot be null or empty |
Explanation |
The message appears in an application program interface (API) method and reflects to an error in the implementation. The error appears when you update the security module configuration. It shows that you did not provide configuration to the update process. |
Action |
When you call a WSClientSecurityProperty#updateRampartConfigElement(OMElement, String) the implementation ensures that the given OMElement argument is not null or empty. Specify a valid entry for the OMElement. |
WSSCME0003 | Invalid value is configured for time-to-live timestamp: ''{0}'' |
Explanation |
The configured time-to-live value for the timestamp used by the security module is invalid. The system expects an integer as a configuration value. |
Action |
Security module configuration for timestamp time-to-live must be an integer. |
WSSCME0004 | Invalid value is configured for max skew timestamp: ''{0}'' |
Explanation |
The configured max skew value for the timestamp used by the security module is invalid. The system expects an integer as a configuration value. |
Action |
Security module configuration for timestamp max skew must be an integer. |
WSSCME0005 | Property name cannot be null or empty |
Explanation |
You updated the security module configuration and did not specify a property for update. |
Action |
The error indicates a severe fault in the Web Services Stack implementation. If the error occurs, report it to the software development team. |
WSSCME0009 | Rampart configuration assertion update error |
Explanation |
The error occurs when xml serialization of an existing rampart configuration assertion fails. Prior to the update, the configuration assertion is serialized to stax stream and parsed with axiom. An invalid rampart configuration assertion can cause the error. |
Action |
If you configure the rampart configuration assertion manually, an invalid configuration can cause the error. Use the Web Services Stack configuration properties instead of providing manual configuration. |
WSSCME0019 | Failed to decode the basic authentication header. |
Explanation |
Web Services Stack security utility failed to decode the received HTTP Basic authentication header. The header should be encoded with base64 encoding. The error suggests that an illegal character (non-ASCII) was found within the header value. |
Action |
Make sure the http client sends an HTTP basic authentication header properly encoded in base64 encoding. |
WSSCMI0000 | Cannot recognize the security configuration key ''{0}''; the key is ignored. |
Explanation |
Rampart configuration updater searches through the client options and dynamic service parameters for keys that refer to the security module configuration. The message is logged when it encounters an unrecognized key. For example, a general purpose key that does not control Rampart specific configuration. |
Action |
None. |
WSSCMW0020 | Axis2 configuration file: '{0}' does not exist. Password change will be disabled. |
Explanation |
The axis2 configuration file is missing. This disables the password change functionality. |
Action |
Contact Software AG global support. |
WSSCMW0021 | Axis2 configuration file: '{0}' cannot be written. Password change will be disabled. |
Explanation |
The axis2 configuration file cannot be written. This disables the password change functionality. |
Action |
Ensure that you can write in the axis2 configuration file. |
WSSCMW0022 | Axis2 configuration URL '{0}' does not denote a valid file path. Password change will be disabled. |
Explanation |
The path to the axis2 configuration file is invalid. |
Action |
Ensure that the URL to the axis2 configuration file is valid and that it is using file protocol. |
WSSCMW0023 | AxisConfiguration instance does not have a valid configuration file URL set. Password change will be disabled. |
Explanation |
AxisConfiguration is missing. |
Action |
Contact SoftwareAG global support. |
WSSCMW0025 | Failed to close input stream to Axis2 configuration file: {0} |
Explanation |
Internal error. Cannot change the axis2 configuration. |
Action |
Contact SoftwareAG global support. |
WSSCMW0026 | Failed to close output stream to Axis2 configuration file: {0} |
Explanation |
Internal error. Cannot change the axis2 configuration. |
Action |
Contact SoftwareAG global support. |
WSSDAE0000 | Unsupported algorithm exception: {0} |
Explanation |
A particular cryptographic algorithm is requested but is not available in the environment. |
Action |
Ensure that you have enabled unlimited strength JCE (Java Cryptographic Extension) on your machine. If you already have it enabled, contact Software AG Global Support. |
WSSDAE0016 | Keystore exception: {0} |
Explanation |
Keystore file can not be proccessed. |
Action |
Ensure that the keystore file is not corrupted and all required certificates are available in it. |
WSSDAE0017 | Key management exception: {0} |
Explanation |
Keystore file can not be proccessed. |
Action |
Ensure that the keystore file is not corrupted and all required certificates are available in it. |
WSSDAE0018 | I/O error reading keystore/truststore file: {0} |
Explanation |
Keystore file can not be proccessed. |
Action |
Ensure that the keystore file is available in the particular location. |
WSSDIE0000 | Invalid or unsupported service scope set to AxisService: {0}. |
Explanation |
The message appears when a service with an invalid scope is created or accessed. The following scopes are supported by Web Services Stack: application; transportsession; soapsession; request. |
Action |
Recreate your service using one of the following scopes: application; transportsession; soapsession; request. |
WSSDIE0001 | Cannot create valid policy manager factory implementation. |
Explanation |
The abstract policy manager factory fails to instantiate the default policy manager factory instance. The default factory implementation class is either not available or the user does not have permissions to access it. |
Action |
Ensure that the wsstack deployer-impl-[VERSION].jar is available on the classpath and the user who starts the java process has the proper permissions to access it. |
WSSDIE0002 | Cannot create valid policy repository factory implementation. |
Explanation |
The abstract policy repository factory fails to instantiate the default policy repository factory instance. The default factory implementation class is either not available or the user does not have permissions to access it. |
Action |
Ensure that the wsstack deployer-impl-[VERSION].jar is available on the classpath and that the user who starts the java process has the proper permissions to access it. |
WSSDIE0003 | Cannot close a policy stream after parsing it. |
Explanation |
Policy supplier cannot close the policy stream after parsing it. |
Action |
Ensure that the stream source is available and it is not locked by another process. |
WSSDIE0004 | Cannot initialize the local policy repository; the axis configuration is not available. |
Explanation |
Axis runtime configuration is not available to the policy repository. This means that the code is not executed in a properly initialized runtime. |
Action |
Ensure that you access the policy repository inside a properly initialized and started wsstack runtime. |
WSSDIE0005 | Cannot create an invalid policies directory; the policy repository is null. |
Explanation |
Invalid policies are automatically moved to a directory inside the policy repository. If the policy repository directory is not available, the invalid policies directory cannot be created. |
Action |
Ensure that the policy repository is properly initialized. |
WSSDIE0006 | Duplicate policy ID; the policy file is moved to {0}. |
Explanation |
The system detects that a policy is deployed with an ID that already exists in the policy repository. The new policy is moved to the invalid policies directory. |
Action |
When you deploy a policy, ensure that a policy with the same ID does not exist in the repository. |
WSSDIE0007 | Cannot verify module support for a policy with the following ID: {0}. |
Explanation |
The policy repository cannot verify whether a policy is supported (all assertions in it are recognized and there are modules deployed in the runtime that handle those assertions). The error occurs when the policy is invalid and/or does not contain any assertions. |
Action |
Ensure that the verified policy is valid and contains valid policy assertions. |
WSSDIE0008 | Policy with the following key: {0} exists in the repository. |
Explanation |
The policy repository contains a policy with the same ID as the policy that is deployed and the "updateIfPresent" flag is set to false. |
Action |
Ensure that the policy does not contain a policy with the same ID as the deployed one or set the flag "updateIfPresent" to true; that enables the update of the existing policy in the repository. |
WSSDIE0009 | An error occurred during policy deployment. |
Explanation |
An unexpected error occurs during policy deployment. |
Action |
Contact Software AG Global Support |
WSSDIE0010 | The given policy does not contain any policy alternatives. |
Explanation |
Cannot verify the policy against modules that support it because it does not contain any policy alternatives. |
Action |
Ensure that the deployed policy is valid and contains at least one policy alternative. |
WSSDIE0011 | Cannot find a module to process the following assertion: {0} |
Explanation |
There is no module deployed in the wsstack runtime that supports the given assertion. |
Action |
If the assertion requires additional processsing by a specific module, ensure that the corresponding module is deployed on the wsstack runtime. |
WSSDIE0012 | The following module: {0}; cannot process the assertion: {1}. |
Explanation |
Although the module is registered to handle a certain policy assertion namespace, the module does not support the particular assertion. |
Action |
Ensure that the policy and all of its assertions are valid and can be processed by the module. |
WSSDIE0013 | Cannot find a policy with the specified ID: {0}. |
Explanation |
You are searching for a policy ID that is not available in the policy repository. |
Action |
Ensure that the policy you use is deployed to the policy repository. |
WSSDIE0014 | The policy XML does not contain an ID, or a name that can be associated with the ID. |
Explanation |
When a policy is deployed to the policy repository, the repository attempts to parse it and get its ID, or its name if an ID is not available. The ID or name afterward is used as a key for retrieving the policy from the repository. If there is no ID or a name in the policy XML, the repository cannot deploy it. |
Action |
Ensure that the policy XML that is deployed in the repository has either a valid (not empty) ID or a valid (not empty) name so that it can be deployed. |
WSSDIE0015 | Cannot find an element with the following name: {0} and the following namespace: {1} in the policy input stream; the policy document is invalid. |
Explanation |
When a policy is deployed to the policy repository, the repository attempts to parse it and get its ID, or its name if an ID is not available. The ID or name is used afterward as a key for retrieving the policy from the repository. If there is no ID or a name in the policy XML the repository cannot deploy it. |
Action |
Ensure that the policy XML includes a name or a wsu:Id attribute declared. |
WSSDIE0016 | An exception occurs while trying to parse the policy input stream. |
Explanation |
The policy repository fails to parse the policy XML stream. |
Action |
Assert that the deployed policy source is a valid XML. |
WSSDIE0017 | Cannot close policy file input stream. |
Explanation |
The policy repository cannot close policy stream after reading it. |
Action |
Ensure that the policy source is available. |
WSSDIE0018 | Cannot initialize local policy repository; the following repository path is incorrect: ''{0}''. |
Explanation |
When the policy repository is initialized it tries to create its directory or use the one that exists. This error occurs when the repository path exists on the file system but it is not a directory. |
Action |
Ensure that the repository path is a directory on the file system or does not exist (so that the policy repository can create it). Alternatively, you can configure another repository path if the configured one cannot be used. |
WSSDIE0019 | Cannot move the following invalid policy file: ''{0}''; to the invalid policies directory. |
Explanation |
The policy repository detects that an invalid policy is deployed. The repository cannot move the invalid policy into the invalid policies directory. |
Action |
Ensure that you deploy a valid XML policy. |
WSSDIE0020 | Cannot load a policy file during policy repository initialization. |
Explanation |
The policy repository fails to deploy a problematic policy file. |
Action |
Ensure that the policy files in the policy repository are valid XML policies. |
WSSDIE0021 | Cannot initialize local policy repository; the following repository path: ''{0}'' does not exist and cannot be created. |
Explanation |
While the policy repository is initialized it checks whether the repository directory exists and if it does not, the repository attempts to create it. This message shows that the creation of the directory fails. The policy repository is not functional. |
Action |
Ensure that either the repository directory exists or the user who starts the java processes is authorized to create it. |
WSSDIE0022 | Cannot initialize a local policy repository; the following repository path is incorrect: ''{0}''. |
Explanation |
When the policy repository is initialized it tries to determine the repository directory path but it fails. The reason is that the code is not invoked inside an initialized wsstack runtime or the wsstack repository directory is not available (in case if a URL configurator is used, for example). |
Action |
Ensure that either the wsstack repository directory is available or configure a specific directory to be used as a policy repository directory. |
WSSDIE0023 | Cannot create a default policy supplier object; the following policy file: ''{0}'' is not a valid file. |
Explanation |
The file argument of the policy file that is deployed through a default policy supplier is either null or does not exist. |
Action |
When you deploy a file through the default policy supplier, ensure that the policy file exists on the file system at the time it is detected by the policy repository. |
WSSDIE0024 | The following policy file does not exist: ''{0}''. |
Explanation |
When a policy stream is retrieved through a default policy supplier instance, the policy file that is used by the supplier is not available. |
Action |
Ensure that the file with the policy you try to access is available in the policy repository. |
WSSDIE0025 | Policy repository location must not be null. |
Explanation |
Policy repository path is not available and therefore the default policy supplier cannot be created since it cannot store the policy in the repository. |
Action |
Ensure that the policy repository is properly initialized. |
WSSDIE0026 | Cannot copy a policy to the repository. |
Explanation |
When a policy stream is deployed through the default policy supplier, the supplier attempts to store the policy in repository directory. However, the copy procedure of the policy file to the repository directory fails. |
Action |
Ensure that the user who starts the java process is authorized to write to the policy repository directory. Another reason for the error is that the stream is closed before policy file is copied. |
WSSDIE0027 | An error occurred during policy deployment while trying to close the file output stream. |
Explanation |
A policy stream is deployed in the policy repository through a default policy supplier instance. While storing the stream to the policy repository directory, the supplier fails to close the original stream. However, the policy XML is successfully stored in the repository and the policy is effectively deployed. |
Action |
None. |
WSSDIE0028 | The following policy repository does not exist and cannot be created: {0}. |
Explanation |
The policy repository directory does not exist and cannot be created. |
Action |
Ensure that the policy repository is properly initialized. Ensure that the user who starts the java process is authorized to write in the specified repository directory. |
WSSDIE0029 | Failed to delete a policy file. |
Explanation |
A policy file deployed through a default policy supplier cannot be deleted. |
Action |
Ensure that the policy file is not locked by another process. |
WSSDIE0138 | Cannot assign a policy to a service; a policy with the following ID cannot be found: ''{0}''. |
Explanation |
The policy manager is requested to assign a policy to a certain service but the policy denoted by the supplied policy ID cannot be found in the policy repository. |
Action |
Ensure that the policy you attach exists in the policy repository. |
WSSDIE0144 | Unsupported IDynamicDescription implementation; the WSPolicyManager implementation works only with dynamic description instances of type {0} but {1} is available. |
Explanation |
Encountered an unrecognized dynamic description instance. Web Services Stack policy manager is intended to work with a specific implementation of the underlying dynamic description. |
Action |
If you use the default Web Services Stack policy manager, implement your dynamic assets so that they extend the default implementation of the deployer API. |
WSSDIE0158 | Service {0} does not use a standard deployment classloader; the resource jar is not appended to the classpath of the classloader. |
Explanation |
Service resource jar cannot be added to the service classpath. The service class loader is not an instance of org.apache.axis2.deployment.DeploymentClassLoader. |
Action |
Contact Software AG Global Support. |
WSSDIE0162 | The method can be called on a deployed unit only. |
Explanation |
The boolean isEngaged(String, boolean) method is called on an AxisDescription instance that has not been deployed on the Web Services Stack runtime yet. Therefore, it has no AxisConfiguration instance associated with it. |
Action |
Assert that the isEngaged module check is invoked on the deployed instance. |
WSSDIE0164 | Web Services Stack policy manager failed to update or remove policy from associated services when handling a "policy file deleted" event fired by the policy repository due to: ''{0}''. |
Explanation |
By default, the Web Services Stack policy manager is registered as a policy repository listener so it is notified when the policy repository detects that a policy file has been deleted. When such an event is received the policy manager attempts to remove the deleted policy from any associated attachment points (services, operations, or messages) and in the course of these actions the error occurs. |
Action |
This is an internal error. Contact Software AG Global Support. |
WSSDIE0165 | Web Services Stack policy manager fails to update or remove policy from associated services when handling a "policy file updated" event fired by the policy repository due to: ''{0}''. |
Explanation |
By default, the Web Services Stack policy manager is registered as a policy repository listener so it is notified when the policy repository detects that a policy file has been updated. When such an event is received the policy manager attempts to remove the policy from any associated attachment points (services, operations, or messages) in case the new policy has a different ID. If the new policy has the same ID as the previously deployed one (true update) it tries to refresh the policy attached to the respective subjects. In the course of these actions the error occurs. |
Action |
This is an internal error. Contact Software AG Global Support. |
WSSDIE0166 | Cannot deploy policy file "{0}" as the policy is invalid. A file with name "{0}" already exists in the invalid policies directory. The existing file is overwritten. |
Explanation |
You try to deploy more than once an invalid policy. A policy file with the same name already exists in the directory, in which invalid policies are maintained. The existing file is overwritten with the new one (the file is updated). |
Action |
Check the policy you want to deploy. |
WSSDIE0167 | The policy ID or name is invalid. The policy is not deployed. |
Explanation |
The policy ID or name, if available, cannot contain whitespace characters inside. If whitespace characters are found inside, the policy is considered invalid and the policy file is moved to the invalid folder. |
Action |
Check the policy ID or name for whitespace characters and remove them, if any. |
WSSDIE0168 | Cannot deploy policy "{0}"; the policy is invalid and cannot be processed. |
Explanation |
There is a problem while processing the policy. The policy file is corrupted or the XML is invalid. |
Action |
Check and validate the policy XML, check for typographical errors, and so on. Finally, deploy the policy again. |
WSSDIE0169 | Failed to roll back disengage of the following module: {0}. |
Explanation |
An error occurs while disengaging modules, the system attempts to re-engage them but the corresponding module fails. |
Action |
Contact Software AG Global Support. |
WSSDIE0170 | Failed to disengage module {0}. Reason: {1} |
Explanation |
While removing policy components for the current DynamicDescription instance, the system attempts to disengage a referenced module but it fails. |
Action |
Contact Software AG Global Support. |
WSSDIE0171 | Exceptions must not be generated when skipping module disengagement. |
Explanation |
Policy cleanup must not generate any exceptions if module disengagement argument is not set. |
Action |
Contact Software AG Global Support. |
WSSDIE0172 | Cannot refresh services after the ''{0}'' policy is updated due to the following: ''{1}''. |
Explanation |
Web Services Stack policy manager is automatically updating policy subjects upon a policy update with a certain ID. The update fails when applying the new policy to the subjects. |
Action |
Contact Software AG Global Support. |
WSSDIE0173 | Failed to create a dynamic deployer instance. |
Explanation |
The exception occurs while trying to initialize the default policy manager instance and it fails to initialize the dynamic deployer. This happens when no valid Axis configuration is found. |
Action |
Ensure that the code is running in properly started and initialized Web Services Stack runtime. |
WSSDIE0174 | Cannot clean policy of the following Web service: ''{0}''. |
Explanation |
The policy manager failed to remove policies for the given Web service. Generally, the exception is generated when the disengageModules flag is set to true. However, this is not what causes the problem in this invocation. |
Action |
Redeploy your Web service. |
WSSDIE0175 | Cannot clean policy of the Web service ''{0}'' operation ''{1}''. |
Explanation |
The policy manager failed to clean the policy on the given operation of the given Web service. Generally, the exception is thrown only when the disengageModules flag is set to true. However, this is not what causes the problem in this invocation. |
Action |
Redeploy your Web service. |
WSSDIE0176 | Cannot clean message policy for service ''{0}'' operation ''{1}''. |
Explanation |
The policy manager failed to clean the message policy on the given operation of the given service. Generally, the exception is thrown only when the disengageModules flag is set to true. However, this is not what causes the problem in this invocation. |
Action |
Redeploy your Web service. |
WSSDIE0178 | Failed to retrieve the following service group after persisting and redeploying it: ''{0}''. |
Explanation |
The Dynamic deployer API was used to persist a service group but after redeploying the service group could not be found in Web Services Stack runtime. A possible cause for the error is a problem during the deployment. |
Action |
Ensure that the service group file or directory is not locked, and the current user has the credentials to write to it. Redeploy your Web service manually. |
WSSDIE0179 | Exception occurs while trying to obtain policy manager instance and the policy manager cannot be notified about redeployed Web services. |
Explanation |
When a service is persisted the Web Services Stack runtime undeploys and redeploys it again. That makes any references kept to the previous Web service invalid. Since the policy manager keeps associations between policies and attachment points (such as Web services) it needs to be notified to synchronize its cache. |
Action |
The system is automatically recovered but the policy manager's cached association for the updated Web services are lost. |
WSSDIE0180 | Failed to retrieve the following Web service ''{0}'' after persisting and redeploying it. |
Explanation |
The Dynamic deployer API was used to persist a Web service but after redeploying the Web service cannot be found in the Web Services Stack runtime. A possible cause for the error is a problem during the deployment. |
Action |
Ensure that the Web service file or directory is not locked and the current user has permissions to write to it. Redeploy your Web service manually. |
WSSDIE0181 | Web Services Stack policy engine failed to parse the deployed policy. |
Explanation |
An exception occurred while the policy engine was processing a freshly deployed policy. Most probably the policy xml is invalid. |
Action |
Correct the policy xml and redeploy it. |
WSSDIE0184 | Security exception during fetch of class field. |
Explanation |
This is an internal error caused by an API inconsistency. |
Action |
Contact SoftwareAG global support. |
WSSDIE0185 | Unreachable field with name {0} in class {1} |
Explanation |
This is an internal error caused by an API inconsistency. |
Action |
Contact SoftwareAG global support. |
WSSDIE0186 | Illegal argument: engageModules passed to method. |
Explanation |
This is an internal error caused by an API inconsistency. |
Action |
Contact SoftwareAG global support. |
WSSDIE0187 | Illegal access to field with name {0} in class {1} |
Explanation |
This is an internal error caused by an API inconsistency. |
Action |
Contact SoftwareAG global support. |
WSSDIE0189 | Failed to read the policy file. |
Explanation |
The policy file could not be read or is invalid. |
Action |
Verify that your policy file is compliant with WS Security specification. |
WSSDIW0163 | Modules cannot be engaged at the following binding hierarchy - Endpoint (port), Binding, Binding operation, Binding Message. |
Explanation |
Axis2 does not support engaging modules at the listed subjects and respectfully calling isEngaged on those axis objects throws an UnsupportedOperationException. |
Action |
Invalid invocation. This method cannot be invoked on IDynamicPort, IDynamicBinding, IDynamicBindingOperation, or IDynamicBindingMessage. |
WSSDIW0177 | Parent service group is not found for the following Web service: ''{0}''. |
Explanation |
The dynamic deployer could not find the parent service group of the given Web service. |
Action |
Ensure that the Web service is properly deployed or redeploy it. |
WSSDIW0190 | Expected dialect "{0}" but found "{1}" ,cannot proceed. |
Explanation |
Found unexpected dialect in the specified request. |
Action |
Set proper dialect. If you are unable to do so, contact Software AG global support. |
WSSDIW0191 | Null or empty policy identifier given, cannot proceed. |
Explanation |
Policy identifier is invalid. |
Action |
Set proper identifier. If you are unable to do so, contact Software AG global support. |
WSSDSE0000 | In order to deploy JAX-WS services you must have a JAX-WS Deployer configured in your axis2.xml. |
Explanation |
The <deployer extension=".jar" directory="servicejars"class="org.apache.axis2.jaxws.framework.JAXWSDeployer"/> line in your axis2.xml is commented or missing. |
Action |
Uncomment the <deployer extension=".jar" directory="servicejars"class="org.apache.axis2.jaxws.framework.JAXWSDeployer"/> line in the axis2.xml, or add it if it is missing. |
WSSDSE0011 | An error occurs while trying to remove the following security provider: ''{0}''. |
Explanation |
Before the SAGAdminServlet is destroyed, it checks whether the BouncyCastle and JuiCE are added to the java security providers and whether they are loaded by the current web application classloader. If it is true, the servlet tries to remove them, as they are not available to other web applications. This error occurs when the servlet tries to cleanup the BouncyCastle and JuiCE providers from the list. |
Action |
Contact Software AG Global Support |
WSSDSE0012 | DeployServlet requires the following instance in the servlet context but cannot find it: ''{0}''. |
Explanation |
An Axis2 "org.apache.axis2.deployment.DeploymentEngine" instance has to be available in Web Services Stack DeployServlet's servlet context under the DEPLOYER servlet context attribute but such an attribute is not found. |
Action |
The reason for the error is that Web Services Stack Administration servlet fails to initialize. Make sure that the servlet is properly initialized. |
WSSDSW0013 | Cannot find the axi2.xml file location in the known locations. |
Explanation |
The axis2 configuration file is missing. |
Action |
Make sure the axis2 configuration file is the proper location. |
WSSDSW0014 | Cannot find the axi2.xml location due to an error. |
Explanation |
The axis2 configuration could not be obtained. |
Action |
Contact SoftwareAG global support. |
WSSJCE0012 | Module ''{0}'' is engaged but configuration for a JAX-WS handler-chain was not found. |
Explanation |
The module is engaged, but it does not contain any JAX-WS handlers configured into the chain. |
Action |
Inspect the engaged module if it contains the expected JAX-WS handlers. |
WSSJCE0015 | The JAX-WS handler chain cannot be loaded. |
Explanation |
The JAX-WS handler-chain descriptor (XML) file is not correct or the handler instances configured in it cannot be loaded. |
Action |
Inspect and correct the JAX-WS handler-chain descriptor (XML) file. |
WSSJCE0018 | An incorrect property value is set for the JAX-WS handler-chain. |
Explanation |
The JAX-WS handler-chain descriptor (XML) file has an incorrect property value set for a JAX-WS handler. |
Action |
Check and correct the JAX-WS handler-chain descriptor (XML) file. |
WSSJCE0019 | An error occurs in the JAX-WS handler-chain execution. |
Explanation |
At the invocation of JAX-WS in/out flow, an exception is thrown while processing the chain. |
Action |
For more information about the failure, see the AxisFault response message. Check the JAX-WS chain configuration. |
WSSJCW0001 | A handler class of the handler chain cannot be found. |
Explanation |
Classes are missing for some handler instances configured into the handler-chain descriptor (XML) file. |
Action |
Check that the handler classes configured into the handler-chain descriptor (XML) file are available into the jar library (class-path). |
WSSJCW0002 | A handler of the handler chain cannot be instantiated. |
Explanation |
A class of the handler available into the classpath is not a standard one. |
Action |
Check that the handler class available into the jar library is the original one provided by the product and was not modified improperly. |
WSSJCW0004 | The configuration of a class from the handler chain is incorrect. |
Explanation |
A class of the handler available into the classpath is not a standard one. |
Action |
Check that the handler class available into the jar library is the original one provided by the product and was not modified improperly. |
WSSJCW0005 | An error occurs while loading the JAX-WS handler chain. |
Explanation |
A class of the handler available into the classpath is not a standard one. |
Action |
Check that the handler class available into the jar library is the original one provided by the product and was not modified improperly. |
WSSJCW0009 | An error occurs while executing PreDestroy methods of the JAX-WS handlers. {0} |
Explanation |
A JAX-WS handler executed into the chain, throws an exception while destroying it after being used. |
Action |
Check that the handler class available into the jar library or its XML configuration file were not modified improperly. |
WSSJCW0011 | An error occurs while executing PostConstruct methods of the JAX-WS handlers. {0} |
Explanation |
A JAX-WS handler executed into the chain throws an exception during its initialization. |
Action |
Check that the handler jar archive or its XML configuration file were not modified improperly. |
WSSJHE0003 | An error occurs during the completion of a JAX-WS handler. |
Explanation |
An error occurs into the flow when closing a JAX-WS handler. |
Action |
Check whether the handler class that is available into the jar library or its XML configuration file are not modified improperly. |
WSSJHE0004 | JAX-WS handler PreDestroy method failed. |
Explanation |
An error occurs when invoking a JAX-WS handler PreDestroy method. |
Action |
Check whether the Handler class that is available into the jar library or its XML configuration file are not modified improperly. |
WSSJHE0008 | A JAX-WS handler failed. |
Explanation |
An error occurs when invoking a JAX-WS handler. |
Action |
Check whether the handler class that is available into the jar library or its XML configuration file are not modified improperly. |
WSSJHE0010 | A JAX-WS handler instantiation failed for the following classname: {0}. |
Explanation |
An error occurs during JAX-WS handler instantiation. |
Action |
Check whether the handler class that is available into the jar library or its XML configuration file are not modified improperly. |
WSSJHE0011 | The JAX-WS handler {1} is not type {0}. |
Explanation |
An error occurs during JAX-WS handler invocation. |
Action |
Check whether the handler class that is available into the jar library or its XML configuration file are not modified improperly. |
WSSJNE0000 | Could not read the value, Illegal state exception. |
Explanation |
The provided JSON data is invalid. |
Action |
Make sure the provided JSON data is valid. |
WSSJNE0001 | IO error while reading JSON stream. |
Explanation |
An error during reading/writing JSON data. |
Action |
Check your connectivity and try again. |
WSSJNE0004 | Could not load configured json type converter ''{0}''. |
Explanation |
Missing JSON type converter class. |
Action |
Make sure that the service archive (aar file) contains a configured JSON type converter class. |
WSSJNE0005 | Could not instantiate configured json type converter ''{0}''. |
Explanation |
Invalid converter class definition. |
Action |
Check the converter class definition. |
WSSJNE0006 | Could not access configured json type converter class ''{0}''. |
Explanation |
Invalid converter class definition. |
Action |
Check the converter class definition. Make your class/default constructor public. |
WSSJNE0007 | Could not load configured json type converter ''{0}''. |
Explanation |
Missing JSON type converter class. |
Action |
Make sure that the service archive (aar file) contains a configured JSON type converter class. |
WSSJNE0008 | Configured json type converter class ''{0}'' cannot be cast to type converter interface class ''{1}''. |
Explanation |
Invalid converter class definition. |
Action |
Check the converter class definition and ensure it implements the type converter interface. |
WSSJNE0014 | Failed to configure type converter, the JSON formatter will use the default type converter. Reason: {0} |
Explanation |
Could not load the configured custom JSON type converter. |
Action |
Ensure the configured custom JSON type converter class is valid and available on the classpath. |
WSSJNW0010 | Could not load configured json type converter ''{0}'' using class loader of service ''{1}'', falling back to Web Services Stack class loader. |
Explanation |
The configured JSON type converter could not be loaded from service archive (aar file) and Web Services Stack will attempt to load it using Web Services Stack class loader. |
WSSJNW0011 | {0} - Ignoring ''{1}'' parameter with null value. |
Explanation |
The configured JSON type converter parameter has a null value. |
Action |
Check the configured 'json.type.converter' parameter definition and ensure it specifies a non-null value. |
WSSJNW0012 | Unable to obtain current element class name due to {0} |
Explanation |
Current class name element could not be obtained. |
Action |
Contact SoftwareAG global support. |
WSSJNW0013 | {0} - Ignoring ''{1}'' parameter with a non-String value ({2}) |
Explanation |
The configured JSON type converter parameter has a non-String value. |
Action |
Check the configured 'json.type.converter' parameter definition and ensure it specifies a String value. |
WSSMRE0003 | The service does not define adapter class parameter: ''{0}''. |
Explanation |
When com.softwareag.wsstack.messagereceivers.AdapterMessageReceiver is invoked, it tries to find a parameter named adapter in the currently invoked service. The adapter parameter denotes a name of a class that implements the com.softwareag.wsstack.adapter.api.Adapter interface. The message receiver attempts to instantiate and execute the configured adapter. |
Action |
Add an adapter parameter to your service definition (in your services.xml file). As a value to the parameter, set the required adapter implementation class. |
WSSMRE0004 | The configured adapter class is invalid: ''{0}'' |
Explanation |
When com.softwareag.wsstack.messagereceivers.AdapterMessageReceiver is invoked, it tries to find a parameter named adapter in the currently invoked service. The adapter parameter denotes a name of a class that implements the com.softwareag.wsstack.adapter.api.Adapter interface. The message receiver attempts to instantiate and execute the configured adapter. |
Action |
Specify a valid adapter class name as a value to the adapter parameter in your service definition. |
WSSOGE0000 | Failed to add service {0} |
Explanation |
Failed to add service. |
Action |
Contact SoftwareAG global support. |
WSSOGE0001 | Failed to handle service modification {0} |
Explanation |
Failed to handle service modification. |
Action |
Contact SoftwareAG global support. |
WSSOGE0002 | Failed to handle service removal {0} |
Explanation |
Failed to handle service removal. |
Action |
Contact SoftwareAG global support. |
WSSOGE0003 | Failed to add service {0} |
Explanation |
Internal error. Failed to add service. |
Action |
Contact SoftwareAG global support. |
WSSOGE0004 | Failed to handle service removal {0} |
Explanation |
Internal error. Failed to handle service removal. |
Action |
Contact SoftwareAG global support. |
WSSOGE0010 | The specified {0} property points to a non-existing or non-readable file. Using default. |
Explanation |
The main axis2.xml configuration file is missing. |
Action |
Make sure that the configured axis2.xml file is in the correct location and is readable. |
WSSOGE0013 | Cannot set axi2.xml URL as axisConfig parameter. |
Explanation |
Internal error. Cannot set the axi2.xml URL as an axisConfig parameter. |
Action |
Contact SoftwareAG global support. |
WSSOGE0016 | Error during module shutdown: {0} |
Explanation |
Internal error. The error occured during module shutdown. |
Action |
Contact SoftwareAG global support. |
WSSOGE0021 | Failed to remove group {0} |
Explanation |
Internal error. Failed to remove group. |
Action |
Contact Software AG global support. |
WSSOGE0023 | Failed to resolve relative resource: {0} from bundle {1} |
Explanation |
Internal error. Failed to resolve resource from a bundle. |
Action |
Contact Software AG global support. |
WSSOGE0025 | Failed to resolve relative resource {0} from bundle {1} |
Explanation |
Internal error. Failed to resolve resource from a bundle. |
Action |
Contact Software AG global support. |
WSSOGE0031 | AxisConfigurator instance (class '{0}') does not derive from {1}, Web Services Stack Deploy Servlet will not be functional. |
Explanation |
Provided axis configurator is not aware of the axis deploy engine. |
Action |
Contact Software AG global support. |
WSSPWE0000 | UsernameToken authentication failed. |
Explanation |
Invalid or empty password provided. |
Action |
Provide valid credentials. |
WSSPWE0001 | Unknown password callback type: {0}. |
Explanation |
Invalid usage of the password callback handler. Valid usage is for signing, decryption, and username password validation. |
Action |
Provide a valid usage of the callback handler. |
WSSPWE0004 | The system cannot load the LDAP configuration for the password callback handler: {0}. |
Explanation |
The password callback handler needs LDAP configuration. If it is not configured, the default LDAP configuration ldap.properties is used. LDAP configuration file cannot be loaded. |
Action |
Provide valid LDAP configuration. |
WSSPWE0008 | Invalid LDAP configuration for the password callback handler. |
Explanation |
One or more of the required LDAP configuration properties are not available in the LDAP configuration. |
Action |
Provide all required LDAP configuration properties. |
WSSPWE0009 | UsernameToken authentication failed. |
Explanation |
Invalid or empty password provided. The user cannot be authenticated. |
Action |
Provide valid, non-empty values for username and password. |
WSSPWE0010 | Cannot recognize the following user ID: ''{0}''. |
Explanation |
Invalid or empty username, or certificate alias provided. |
Action |
Check the spelling and provide a valid, non-empty value for username, or certificate alias (depending on the use case). |
WSSPWE0012 | System cannot load the password callback handler configuration file: {0}. |
Explanation |
The password callback handler configuration file is not found and cannot be loaded. |
Action |
Check if the configuration file exists and if the path to the file is correct. |
WSSPWE0013 | Cannot convert the configuration from a stream to an OMElement: {0}. |
Explanation |
A problem occurs while converting the configuration file content to an OMElement. |
Action |
Check and validate the XML format of the configuration file. |
WSSRME0000 | Exception on callback. |
Explanation |
Internal error. Failed to receive message on callback. |
Action |
Contact Software AG global support. |
WSSRME0001 | Exception on callback. |
Explanation |
Internal error. Failed to receive message on callback. |
Action |
Contact Software AG global support. |
WSSTLW0013 | Password must comply with 3 out of the following 4 rules: at least 1 uppercase character, 1 lowercase character, 1 digit, and 1 special character. Minimum password length is 10 characters. |
WSSTRE0001 | Cannot close the input stream of the file; the file absolute path value is [{0}]. The exception message is: {1}. |
Explanation |
Cannot close a file input stream or cannot release system resources associated with the stream. |
Action |
Check the file state. For example, it can be locked by another process. |
WSSTRE0002 | The used key cannot be "null". |
Explanation |
The key that is used for a property is null. |
Action |
Contact Software AG Global Support. |
WSSTRE0003 | Cannot close an input/output stream of type [{0}]; the exception message is: {1} |
Explanation |
There is an exception during input/output stream closure. |
Action |
Contact Software AG Global Support. |
WSSTRE0004 | There is an error while manipulating an input/output stream in use. |
Explanation |
There is an exception during input/output stream processing. |
Action |
Contact Software AG Global Support. |
WSSTRE0005 | The repository listener is not initialized. |
Explanation |
The repository listener is not initialized. |
Action |
Contact Software AG Global Support. |
WSSTRE0006 | The following operation is not supported: [{0}]. |
Explanation |
Non existing operation requested. |
Action |
Check that an operation with the specified name exists. Contact Software AG Global Support. |
WSSTRE0007 | Cannot delete the file with the following file path: [{0}]. |
Explanation |
There is a problem deleting the file. |
Action |
Check that the file exists and it is not locked. Check that you have sufficient permissions to delete the file. |
WSSTRE0008 | Cannot create a directory in the following location: [{0}]. |
Explanation |
There is a problem while creating a "services" directory. |
Action |
Contact Software AG Global Support. |
WSSTRE0009 | The following Web service element cannot be null: {0}. |
Explanation |
The Web service element is null. |
Action |
Check the content structure of the Web service that is deployed dynamically. |
WSSTRE0010 | The name of the Web service client {0} must not be null or empty. |
Explanation |
The name of the Web service client that is instantiated is null or empty. |
Action |
Check the Web service client implementation. |
WSSTRE0011 | Cannot delete the following directory: [{0}]. |
Explanation |
There is a problem while deleting a Web service directory. |
Action |
Check that the Web service directory is not locked and check that you have sufficient permissions to delete the directory. |
WSSXTE0000 | {0}: An XML document that is empty, invalid or does not exist. |
Explanation |
The document is empty or invalid. |
Action |
Provide a valid, non-empty XML document. |
WSSXTE0013 | Unexpected element found after the SOAP Body element: ''{0}'' |
Explanation |
Web Services Stack is processing an invalid message. The sent message contains an unexpected element in the SOAP Envelope after the SOAP Body element. A SOAP Envelope is expected to contains only an optional SOAP Header element followed by one SOAP Body element. |
Action |
Inform the web service conversation partner that they are generating invalid web service messages. |
WSSXTE0014 | Unexpected element found after the SOAP envelope has been consumed: ''{0}'' |
Explanation |
Web Services Stack is processing an invalid message. The sent message contains an unexpected element after the already consumed SOAP Envelope. A web service message is expected to contain a single SOAP Envelope element. |
Action |
Inform the web service conversation partner that they are generating invalid web service messages. |
WSSXTE0016 | Failed to marshall response object. |
Explanation |
Internal error. Failed to marshall response object. |
Action |
Contact Software AG global support. |
WSSXTE0017 | Could not close piped output stream. |
Explanation |
Internal error. Could not close piped output stream. |
Action |
Contact Software AG global support. |
WSSXTE0018 | Invalid timeout value format: not a number. |
Explanation |
Illegal number for timeout config parameter. |
Action |
Check timeout parameters: SO_TIMEOUT, CONNECTION_TIMEOUT |
WSSXTW0019 | Could not obtain inbound message context. |
Explanation |
The obtained axis2 message context is invalid. |
Action |
Contact SoftwareAG global support. |