Explanation | An application manifest, APPLICATION.MF, must contain both Application-SymbolicName and Application-Version headers. |
Action | Edit the APPLICATION.MF file to add the missing header or headers. |
Explanation | The Deployed-Content header in the deployment manifest, DEPLOYMENT.MF, is not valid. |
Action | If you provided this file, correct the contents of the Deployed-Content header. |
Explanation | The application content is ambiguous or not valid. |
Action | Check and correct the source of the content, if possible. |
Explanation | A deployment manifest, DEPLOYMENT.MF file, must contain a valid deployed-version header. |
Action | If you provided the DEPLOYMENT.MF file, check that it contains a valid deployed-version header. |
Explanation | A service has been declared with a filter expression that is not valid. |
Action | Locate and correct the filter expression. |
Explanation | A bundle manifest cannot be extracted because the location is not a valid file or directory. |
Action | If you provided this location, check that it is valid and that it exists. |
Explanation | A bundle manifest cannot be processed because at least one element does not contain a required quotation mark. |
Action | Locate and correct the specified bundle manifest. |
Explanation | A manifest header cannot be parsed because it contains a version attribute that is not valid. |
Action | Locate and correct the version according to the OSGi version specification. |
Explanation | A manifest header cannot be parsed because it contains an empty version attribute. |
Action | Locate and correct the relevant header. |
Explanation | A file that must contain exact versions only, such as a deployment manifest, DEPLOYMENT.MF, contains a range of versions. |
Action | Locate and correct the relevant header. |
Explanation | The product needs to create a temporary directory but cannot. |
Action | Check that storage space exists, and that the product has the necessary permissions to create the directory. |
Explanation | An entry in the Import-Service header of the application manifest, APPLICATION.MF, is not valid. |
Action | Locate and correct the relevant header. |
Explanation | An entry in the Export-Service header of the application manifest, APPLICATION.MF, is not valid. |
Action | Locate and correct the relevant header. |
Explanation | An entry in the Application-Roles header of the application manifest, APPLICATION.MF, is not valid. |
Action | Locate and correct the relevant header. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | The Deployed-Use-Bundle header in the deployment manifest, DEPLOYMENT.MF is not valid. |
Action | If you provided this file, correct the contents of the Use-Bundle header. |
Explanation | The Provision-Bundle header in the deployment manifest, DEPLOYMENT.MF is not valid. |
Action | If you provided this file, correct the contents of the Provision-Bundle header. |
Explanation | Two web application bundle (WAB) files in the enterprise bundle archive (EBA) file have the same bundle symbolic name, version, and Web-ContextPath. |
Action | Ensure that the EBA file contains the correct WAB files. |
Explanation | A bundle file in the enterprise bundle archive (EBA) file has no bundle manifest, MANIFEST.MF. This bundle cannot serve web content and might not operate correctly. |
Action | Ensure that the bundle file contains a valid bundle manifest file. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | The bundle manifest, MANIFEST.MF, for a bundle in the enterprise bundle archive (EBA) file cannot be read. This bundle cannot serve web content and might not operate correctly. |
Action | Ensure that the bundle file contains a valid manifest file. |
Explanation | The DeployedService-Import header in a deployment manifest, DEPLOYMENT.MF, is not valid. |
Action | If you provided the deployment manifest, correct the contents of the DeployedService-Import header. |
Explanation | The bundles listed in the Deployed-Content header in the DEPLOYMENT.MF file must match the bundles listed in the Application-Content header in the APPLICATION.MF file. The bundle version in the Deployed-Content header in the DEPLOYMENT.MF file must be within the version range for the corresponding bundle in the Application-Content header in the APPLICATION.MF file. |
Action | If you provided the deployment manifest, correct the contents of the Deployed-Content header in the DEPLOYMENT.MF file. Ensure that each bundle is listed in both the Deployed-Content header in the DEPLOYMENT.MF file and the Application-Content header in the APPLICATION.MF file, and that the bundle version in the Deployed-Content header in the DEPLOYMENT.MF file is within the version range for the corresponding bundle in the Application-Content header in the APPLICATION.MF file. |
Explanation | The bundles listed in the Deployed-Use-Bundle header in the DEPLOYMENT.MF file must also be listed in the Use-Bundle header in the APPLICATION.MF file. The bundle version in the Deployed-Use-Bundle header in the DEPLOYMENT.MF file must be within the version range for the corresponding bundle in the Use-Bundle header in the APPLICATION.MF file. The Use-Bundle header in the APPLICATION.MF file can list additional bundles that are not listed in the Deployed-Use-Bundle header of the DEPLOYMENT.MF file. |
Action | If you provided the deployment manifest, correct the contents of the Deployed-Use-Bundle header in the DEPLOYMENT.MF file. Ensure that each bundle listed in the Deployed-Use-Bundle header in the DEPLOYMENT.MF file is also listed in the Application-Content header of the APPLICATION.MF file, and that the bundle version in the Deployed-Use-Bundle header of the DEPLOYMENT.MF file is within the version range for the corresponding bundle in the Use-Bundle header in the APPLICATION.MF file. |
Explanation | The WAS-Feature-Required header in the deployment manifest, DEPLOYMENT.MF, is not valid. |
Action | If you provided the deployment manifest, correct the contents of the WAS-Feature-Required header. |
Explanation | The Application-SymbolicName in the application manifest, APPLICATION.MF, and deployment manifest, DEPLOYMENT.MF, do not match. |
Action | Check that the correct file is provided, and ensure the values of Application-SymbolicName in the APPLICATION.MF and DEPLOYMENT.MF are the same. |
Explanation | The Application-Version in the application manifest, APPLICATION.MF, and deployment manifest, DEPLOYMENT.MF, do not match. |
Action | Check that the correct file is provided, and ensure the values of Application-Version in the APPLICATION.MF and DEPLOYMENT.MF are the same. |
Explanation | The Application-SymbolicName and Application-Version in the application manifest, APPLICATION.MF, and deployment manifest, DEPLOYMENT.MF, do not match. |
Action | Check that the correct file is provided, and ensure the values of Application-SymbolicName and Application-Version in the APPLICATION.MF and DEPLOYMENT.MF are the same. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | The bundle needs to be expanded so that it can be used by another bundle that is referring to it by reference. |
Action | Either change the application so that it does not refer to the bundle, or investigate the cause of the exception. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | The internal bundle cache found a file for the bundle, but could not verify the bundle manifest in the file. |
Action | Delete the failing bundle from the bundle cache and download it again. If the problem persists then check whether the bundle in the bundle repository is valid. |
Explanation | The Apache Aries container could not install the bundle. |
Action | Check previous Apache Aries messages for details of the failure. |
Explanation | The deployment manifest for the bundle could not be parsed. |
Action | Check that the deployment manifest is correctly formatted. |
Explanation | The deployment manifest for the application contains an incorrectly formatted service import. |
Action | Check that the application correctly specifies the services that it imports, then try again to deploy the application. |