Explanation | Bundle repository was configured with a file that is not a valid OSGi bundle. |
Action | Ensure that the file is a valid OSGi bundle or exclude it from the bundle repository. |
Explanation | The executor service is not available. Asynchronous tasks such as repository configuration are not possible. |
Action | Check the logs for earlier startup failures. |
Explanation | A required service cannot be found. Some functions and operations which rely on this service may not be possible. |
Action | Check your server configuration to ensure that the services are present and configure correctly. |
Explanation | An error occurred whilst trying to resolve one or more relative URLs. |
Action | Further information on the underlying cause of this issue is available in the log files. |
Explanation | The remote repository XML file contained an invalid URI for one of it's resources. |
Action | Correct the invalid URI in the remote repository XML. |
Explanation | The specified location does not exist or cannot otherwise be resolved. |
Action | Check that the supplied location is valid. |
Explanation | The specified location must resolve to a file. |
Action | Check that the location exists and specifies a file. |
Explanation | An error occurred whilst attempting to download a remote resource. |
Action | Check the FFDC and server logs for more information on the underlying error. |
Explanation | The implementation of Java used to run the server does not supported the requested hashing algorithm. The local cache requires a hashing algorithm and has been disabled. Applications will still be provisioned. |
Action | Change the version of Java to one that supports the requested algorithm. |
Explanation | The property file associated with a remote repository could not be loaded. |
Action | Check the FFDC and server logs for more information on the underlying error. |
Explanation | The property file associated with a remote repository could not be saved. |
Action | Check the FFDC and server logs for more information on the underlying error. |
Explanation | When connecting to the specified remote server an error code was returned. |
Action | Contact the remote server administrator. |
Explanation | A connection is being made to another server in order to download bundles from a remote repository. |
Action | Update the bundle repository configuration if this remote repository should no longer be used. |
Explanation | The remote repository connection has been specified with a protocol that is not supported. |
Action | Update the bundle repository configuration to use a supported protocol. |
Explanation | The remote repository connection has been specified with a protocol that is not recognised. |
Action | Update the bundle repository configuration to use a recognised and supported protocol. |
Explanation | The collective controller feature must be enabled for the server to process the request. |
Action | Enable the collective controller feature in the target server, or direct the request to a server that has the collective controller feature already enabled. |
Explanation | The Java Servlet feature, 3.0 or 3.1, must be enabled for the server to process the request. |
Action | Enable the Java Servlet feature, 3.0 or 3.1, in the target server, or direct the request to a server that has the Java Servlet feature already enabled. |