Объяснение | An IOException occurred when writing a migrated enterprise bundle archive (EBA) file. |
Действие | Check that the product has the necessary permissions to write to the relevant directory, that the target file is not locked, and that storage space is available. |
Объяснение | An IOException occurred when reading an enterprise bundle archive (EBA) application manifest file. The file might be corrupt or unreadable. |
Действие | Check that the application manifest file, APPLICATION.MF, is not damaged or unreadable. |
Объяснение | This exception is unexpected. The cause is not immediately known. |
Действие | 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/ |
Объяснение | This exception is unexpected. The cause is not immediately known. |
Действие | 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/ |
Объяснение | This exception is unexpected. The cause is not immediately known. |
Действие | 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/ |
Объяснение | An IOException occurred when locating the manifest of a JAR file in an enterprise bundle archive (EBA) file. The file might be corrupt or unreadable. |
Действие | Check that the file has the appropriate permissions and that it is in the correct format. |
Объяснение | An IOException occurred when reading an enterprise bundle archive (EBA) file. The file might be corrupt or unreadable. |
Действие | Check that the file has the appropriate permissions and that it is in the correct format. |
Объяснение | The system processed a Web application archive (WAR) without an associated application descriptor file, application.xml, which defines context roots. Context roots for the migrated WAR file will be set to default values. |
Действие | If an application descriptor file is required, check that it is provided and correctly packaged into the enterprise bundle archive (EBA) file. |
Объяснение | An IOException occurred when reading the Java EE application descriptor file in an enterprise bundle archive (EBA) file. |
Действие | Check that the application descriptor file is not corrupted, that it is readable and that it has appropriate permissions set. |
Объяснение | Web application archive (WAR) files in an enterprise bundle archive (EBA) must be converted to Web application bundles (WABs) before they can be deployed. The conversion process did not complete successfully. |
Действие | Check that the WAR file is valid. |
Объяснение | An enterprise bundle archive (EBA) file must contain at least one valid OSGi bundle or Web application archive (WAR) file, or list at least one OSGi bundle in the Application-Content header of its application manifest file. |
Действие | Modify the EBA file to contain at least one valid bundle or WAR (included by value) or list at least one bundle in the in the Application-Content header of its application manifest file, application.mf (included by reference). |
Объяснение | An enterprise bundle archive (EBA) file contains an empty Application-Content header in its application manifest, application.mf. If provided, this entry must list at least one valid bundle. |
Действие | Modify the Application-Content header in the application.mf file. |
Объяснение | This exception is unexpected. The cause is not immediately known. |
Действие | 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/ |
Объяснение | The validation and migration of the enterprise bundle archive (EBA) file completed with errors. |
Действие | See the accompanying error messages in the SystemOut.log file for further information. |
Объяснение | The system cannot resolve the locations of the constituent application bundles, at appropriate versions, of the enterprise bundle archive (EBA) file. |
Действие | See the exception for further information. |
Объяснение | This exception is unexpected. The cause is not immediately known. |
Действие | 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/ |
Объяснение | This exception is unexpected. The cause is not immediately known. |
Действие | 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/ |
Объяснение | This exception is unexpected. The cause is not immediately known. |
Действие | 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/ |
Объяснение | This exception is unexpected. The cause is not immediately known. |
Действие | 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/ |
Объяснение | This exception is unexpected. The cause is not immediately known. |
Действие | 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/ |
Объяснение | Attempted to map a Web application bundle (WAB) to a virtual host that is not valid. |
Действие | Check that the specified virtual host exists. |
Объяснение | You attempted to add an asset that requires one or more bundles to be downloaded from a repository. Either the download has not started, or it is not yet complete. |
Действие | If you did not saved changes after you imported the asset, save the changes now. Wait for the bundle download to complete, then try again to add the asset to the business-level application (BLA). You can view the bundle download status of the asset from the asset detail panel in the administrative console. |
Объяснение | An authentication alias must exist in the global or target security domain when Blueprint resource references are bound. |
Действие | Select an authentication alias that exists in the global or target security domain, or create a suitable authentication alias. |
Объяснение | Authentication aliases with an authentication type of Application cannot be bound to Blueprint resource references. |
Действие | Remove the authentication alias from the relevant resource reference. |
Объяснение | This exception is unexpected. The cause is not immediately known. |
Действие | 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/ |
Объяснение | This exception is unexpected. The cause is not immediately known. |
Действие | 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/ |
Объяснение | The specified directory cannot be created. |
Действие | Check that storage space exists, and that the product has the necessary permissions to create the directory. |
Объяснение | The specified directory cannot be created. |
Действие | Check that storage space exists, and that the product has the necessary permissions to create the directory. |
Объяснение | The specified directory cannot be created. |
Действие | Check that storage space exists, and that the product has the necessary permissions to create the directory. |
Объяснение | The system cannot resolve the selected bundle versions. The bundles might have missing dependencies, be incompatible, or not exist. |
Действие | Modify the selected set of input bundles and try again. You can use the administrative console to view or preview the status of the asset. |
Объяснение | This exception is unexpected. The cause is not immediately known. |
Действие | 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/ |
Объяснение | This exception is unexpected. The cause is not immediately known. |
Действие | 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/ |
Объяснение | This exception is unexpected. The cause is not immediately known. |
Действие | 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/ |
Объяснение | An enterprise bundle archive (EBA) that includes resource references in a Web application archive (WAR) specifies a JNDI name for a resource reference that does not exist in the JNDI namespace. |
Действие | If the resource reference should be in the JNDI namespace, either bind an object to the name, or correct the resource reference and update the EBA. |
Объяснение | To deploy an asset onto more than one target, all targets must be in the same security domain. |
Действие | Change the deployment targets to choose a set that are in a single security domain. |
Объяснение | You imported an asset that requires one or more bundles to download from a repository before you can add the asset to business-level application (BLA). To start the download process, save your changes to the master configuration. |
Действие | After the asset import completes, save your changes, wait for the bundle download to complete, then add the asset to the BLA. You can view the bundle download status of the asset from the asset detail panel in the administrative console. |
Объяснение | Conversion of utility Java archive (JAR) files and Enterprise JavaBeans (EJB) JAR files is not supported. |
Действие | Check that no bundle or Web application bundle (WAB) depends on classes from the JAR file. To avoid the warning message, remove the JAR file from the enterprise bundle archive (EBA). |
Объяснение | An enterprise bundle archive (EBA) asset can be in only a single business-level application (BLA). |
Действие | Create a new application with the same content but with a different application symbolic name. Import the new application as an EBA asset, then add it to this BLA. |
Объяснение | Attempted to map users or groups to a security role that does not exist. |
Действие | Check that the specified security role exists, or create the role in the application. |
Объяснение | Attempted to map a security role to a user that is not valid. |
Действие | Check that the specified user exists. |
Объяснение | Attempted to map a security role to a group that is not valid. |
Действие | Check that the specified group exists. |
Объяснение | The application is not correctly configured. A shared bundle cannot import a package from an isolated bundle. Bundles that are listed in the Application-Content header are isolated and can provide packages only to other bundles listed in that header. |
Действие | Change the packaging or configuration of the application so that bundles that are listed in the Use-Bundle header, or added by the resolver, do not require packages from bundles that are listed in the Application-Content header. |
Объяснение | The application is not correctly configured. A shared bundle cannot consume a service from an isolated bundle. Bundles that are listed in the Application-Content header are isolated and can export services only to other applications through the Application-ExportService mechanism. |
Действие | Change the packaging or configuration of the application so that bundles that are listed in the Use-Bundle header, or added by the resolver, do not require services that are provided by bundles that are listed in the Application-Content header. |
Объяснение | For bundles that are listed in the Application-Content header in APPLICATION.MF, all imports for a given package must have compatible version requirements. |
Действие | Change the packaging or configuration of the application so that all bundles that are listed in the Application-Content header have compatible package version requirements. |
Объяснение | Bundle names that are listed in the Application-Content header of APPLICATION.MF cannot also be listed in the Use-Bundle header, regardless of bundle versions. |
Действие | Change the packaging of the Enterprise Bundle Archive (EBA) so that bundle names are not duplicated in the Application-Content and Use-Bundle headers. |
Объяснение | The specified file could not be parsed. |
Действие | Check that the file is formatted correctly and not corrupted. |
Объяснение | For bundles listed in the Application-Content header in APPLICATION.MF, all package imports must have attributes that can be satisfied at deployment. |
Действие | Change the packaging or configuration of the application so that all bundles that are listed in the Application-Content header have package imports that can be satisfied at deployment. |
Объяснение | The required feature could not be found on any of the servers. |
Действие | Install the required feature on at least one of the servers. |
Объяснение | You attempted to convert an enterprise archive (EAR) file to an enterprise bundle archive (EBA) file when the EAR contains a MANIFEST.MF with an Extension-List header, but conversion of this header is not supported. An EAR file uses the Extension-List header to identify external JARs that the application requires at run time. |
Действие | Ensure that the external JARs that are listed in the Extension-List header are available as bundles in the bundle repository. |
Объяснение | The update of an OSGi application asset with a new binary is not yet supported. |
Действие | If you need to do more than update the bundle versions within the existing asset, please uninstall the asset before importing its replacement. |