Objaśnienie | An IOException occurred when writing a migrated enterprise bundle archive (EBA) file. |
Działanie | 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. |
Objaśnienie | An IOException occurred when reading an enterprise bundle archive (EBA) application manifest file. The file might be corrupt or unreadable. |
Działanie | Check that the application manifest file, APPLICATION.MF, is not damaged or unreadable. |
Objaśnienie | This exception is unexpected. The cause is not immediately known. |
Działanie | 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/ |
Objaśnienie | This exception is unexpected. The cause is not immediately known. |
Działanie | 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/ |
Objaśnienie | This exception is unexpected. The cause is not immediately known. |
Działanie | 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/ |
Objaśnienie | 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. |
Działanie | Check that the file has the appropriate permissions and that it is in the correct format. |
Objaśnienie | An IOException occurred when reading an enterprise bundle archive (EBA) file. The file might be corrupt or unreadable. |
Działanie | Check that the file has the appropriate permissions and that it is in the correct format. |
Objaśnienie | 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. |
Działanie | If an application descriptor file is required, check that it is provided and correctly packaged into the enterprise bundle archive (EBA) file. |
Objaśnienie | An IOException occurred when reading the Java EE application descriptor file in an enterprise bundle archive (EBA) file. |
Działanie | Check that the application descriptor file is not corrupted, that it is readable and that it has appropriate permissions set. |
Objaśnienie | 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. |
Działanie | Check that the WAR file is valid. |
Objaśnienie | 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. |
Działanie | 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). |
Objaśnienie | 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. |
Działanie | Modify the Application-Content header in the application.mf file. |
Objaśnienie | This exception is unexpected. The cause is not immediately known. |
Działanie | 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/ |
Objaśnienie | The validation and migration of the enterprise bundle archive (EBA) file completed with errors. |
Działanie | See the accompanying error messages in the SystemOut.log file for further information. |
Objaśnienie | The system cannot resolve the locations of the constituent application bundles, at appropriate versions, of the enterprise bundle archive (EBA) file. |
Działanie | See the exception for further information. |
Objaśnienie | This exception is unexpected. The cause is not immediately known. |
Działanie | 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/ |
Objaśnienie | This exception is unexpected. The cause is not immediately known. |
Działanie | 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/ |
Objaśnienie | This exception is unexpected. The cause is not immediately known. |
Działanie | 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/ |
Objaśnienie | This exception is unexpected. The cause is not immediately known. |
Działanie | 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/ |
Objaśnienie | This exception is unexpected. The cause is not immediately known. |
Działanie | 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/ |
Objaśnienie | Attempted to map a Web application bundle (WAB) to a virtual host that is not valid. |
Działanie | Check that the specified virtual host exists. |
Objaśnienie | 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. |
Działanie | 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. |
Objaśnienie | An authentication alias must exist in the global or target security domain when Blueprint resource references are bound. |
Działanie | Select an authentication alias that exists in the global or target security domain, or create a suitable authentication alias. |
Objaśnienie | Authentication aliases with an authentication type of Application cannot be bound to Blueprint resource references. |
Działanie | Remove the authentication alias from the relevant resource reference. |
Objaśnienie | This exception is unexpected. The cause is not immediately known. |
Działanie | 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/ |
Objaśnienie | This exception is unexpected. The cause is not immediately known. |
Działanie | 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/ |
Objaśnienie | The specified directory cannot be created. |
Działanie | Check that storage space exists, and that the product has the necessary permissions to create the directory. |
Objaśnienie | The specified directory cannot be created. |
Działanie | Check that storage space exists, and that the product has the necessary permissions to create the directory. |
Objaśnienie | The specified directory cannot be created. |
Działanie | Check that storage space exists, and that the product has the necessary permissions to create the directory. |
Objaśnienie | The system cannot resolve the selected bundle versions. The bundles might have missing dependencies, be incompatible, or not exist. |
Działanie | 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. |
Objaśnienie | This exception is unexpected. The cause is not immediately known. |
Działanie | 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/ |
Objaśnienie | This exception is unexpected. The cause is not immediately known. |
Działanie | 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/ |
Objaśnienie | This exception is unexpected. The cause is not immediately known. |
Działanie | 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/ |
Objaśnienie | 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. |
Działanie | 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. |
Objaśnienie | To deploy an asset onto more than one target, all targets must be in the same security domain. |
Działanie | Change the deployment targets to choose a set that are in a single security domain. |
Objaśnienie | 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. |
Działanie | 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. |
Objaśnienie | Conversion of utility Java archive (JAR) files and Enterprise JavaBeans (EJB) JAR files is not supported. |
Działanie | 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). |
Objaśnienie | An enterprise bundle archive (EBA) asset can be in only a single business-level application (BLA). |
Działanie | 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. |
Objaśnienie | Attempted to map users or groups to a security role that does not exist. |
Działanie | Check that the specified security role exists, or create the role in the application. |
Objaśnienie | Attempted to map a security role to a user that is not valid. |
Działanie | Check that the specified user exists. |
Objaśnienie | Attempted to map a security role to a group that is not valid. |
Działanie | Check that the specified group exists. |
Objaśnienie | 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. |
Działanie | 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. |
Objaśnienie | 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. |
Działanie | 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. |
Objaśnienie | For bundles that are listed in the Application-Content header in APPLICATION.MF, all imports for a given package must have compatible version requirements. |
Działanie | 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. |
Objaśnienie | 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. |
Działanie | Change the packaging of the Enterprise Bundle Archive (EBA) so that bundle names are not duplicated in the Application-Content and Use-Bundle headers. |
Objaśnienie | The specified file could not be parsed. |
Działanie | Check that the file is formatted correctly and not corrupted. |
Objaśnienie | For bundles listed in the Application-Content header in APPLICATION.MF, all package imports must have attributes that can be satisfied at deployment. |
Działanie | 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. |
Objaśnienie | The required feature could not be found on any of the servers. |
Działanie | Install the required feature on at least one of the servers. |
Objaśnienie | 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. |
Działanie | Ensure that the external JARs that are listed in the Extension-List header are available as bundles in the bundle repository. |
Objaśnienie | The update of an OSGi application asset with a new binary is not yet supported. |
Działanie | If you need to do more than update the bundle versions within the existing asset, please uninstall the asset before importing its replacement. |