Explanation | An IOException occurred when writing a migrated enterprise bundle archive (EBA) file. |
Action | 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. |
Explanation | An IOException occurred when reading an enterprise bundle archive (EBA) application manifest file. The file might be invalid, corrupted or unreadable. |
Action | Check that the application manifest file, APPLICATION.MF, follows the specification for manifest files. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | 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. |
Action | Check that the file has the appropriate permissions and that it is in the correct format. |
Explanation | An IOException occurred when reading an enterprise bundle archive (EBA) file. The file might be corrupt or unreadable. |
Action | Check that the file has the appropriate permissions and that it is in the correct format. |
Explanation | 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. |
Action | If an application descriptor file is required, check that it is provided and correctly packaged into the enterprise bundle archive (EBA) file. |
Explanation | An IOException occurred when reading the Java EE application descriptor file in an enterprise bundle archive (EBA) file. |
Action | Check that the application descriptor file is not corrupted, that it is readable and that it has appropriate permissions set. |
Explanation | 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. |
Action | Check that the WAR file is valid. |
Explanation | 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. |
Action | 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). |
Explanation | 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. |
Action | Modify the Application-Content header in the application.mf file. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | The validation and installation of the enterprise bundle archive (EBA) file completed with errors. |
Action | See the accompanying error messages in the SystemOut.log file for further information. |
Explanation | The system cannot resolve the locations of the constituent application bundles, at appropriate versions, of the enterprise bundle archive (EBA) file. |
Action | See the exception for further information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | Attempted to map a web application bundle (WAB) to a virtual host that is not valid. |
Action | Check that the specified virtual host exists. |
Explanation | 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. |
Action | 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. |
Explanation | An authentication alias must exist in the global or target security domain when Blueprint resource references are bound. |
Action | Select an authentication alias that exists in the global or target security domain, or create a suitable authentication alias. |
Explanation | Authentication aliases with an authentication type of Application cannot be bound to Blueprint resource references. |
Action | Remove the authentication alias from the relevant resource reference. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | The specified directory cannot be created. |
Action | Check that storage space exists, and that the product has the necessary permissions to create the directory. |
Explanation | The specified directory cannot be created. |
Action | Check that storage space exists, and that the product has the necessary permissions to create the directory. |
Explanation | The specified directory cannot be created. |
Action | Check that storage space exists, and that the product has the necessary permissions to create the directory. |
Explanation | The system cannot resolve the selected bundle versions. The bundles might have missing dependencies, be incompatible, or not exist. |
Action | 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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | 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. |
Action | 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. |
Explanation | To deploy an asset onto more than one target, all targets must be in the same security domain. |
Action | Change the deployment targets to choose a set that are in a single security domain. |
Explanation | The new or updated asset requires one or more bundles to be downloaded from a repository before it can be added to a composition unit or updated in a composition unit. |
Action | To start the bundle download process, save your changes to the master configuration. You can view the bundle download status of the asset from the asset detail panel in the administrative console. After the bundle downloads are complete, try again to add or update the asset in a composition unit. |
Explanation | Conversion of utility Java archive (JAR) files and Enterprise JavaBeans (EJB) JAR files is not supported. |
Action | 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). |
Explanation | An enterprise bundle archive (EBA) asset can be in only a single business-level application (BLA). |
Action | 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. |
Explanation | Attempted to map users or groups to a security role that does not exist. |
Action | Check that the specified security role exists, or create the role in the application. |
Explanation | Attempted to map a security role to a user that is not valid. |
Action | Check that the specified user exists. |
Explanation | Attempted to map a security role to a group that is not valid. |
Action | Check that the specified group exists. |
Explanation | 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. |
Action | 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. |
Explanation | 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. |
Action | 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. |
Explanation | For bundles that are listed in the Application-Content header in APPLICATION.MF, all imports for a given package must have compatible version requirements. |
Action | 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. |
Explanation | 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. |
Action | Change the packaging of the Enterprise Bundle Archive (EBA) so that bundle names are not duplicated in the Application-Content and Use-Bundle headers. |
Explanation | The specified file could not be parsed. |
Action | Check that the file is formatted correctly and not corrupted. |
Explanation | For bundles listed in the Application-Content header in APPLICATION.MF, all package imports must have attributes that can be satisfied at deployment. |
Action | 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. |
Explanation | The required feature could not be found on any of the servers. |
Action | Install the required feature on at least one of the servers. |
Explanation | 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. |
Action | Ensure that the external JARs that are listed in the Extension-List header are available as bundles in the bundle repository. |
Explanation | The update of an OSGi application asset with a new binary is not supported. |
Action | If you need to do more than update the bundle versions within the existing asset, you must uninstall the asset before importing its replacement. Alternatively, you can add new bundles to an existing application by packaging them in a composite bundle archive (CBA) and adding the CBA as an extension to the composition unit. |
Explanation | In order for an OSGi application to be installed on a cluster, every member of the cluster needs to have all the required features of the application. When adding a new cluster member, that member also needs to have all the features required by all the OSGi applications that are installed on the cluster. |
Action | Check that the proposed member of the cluster has all the required features for the OSGi application listed in the error message. |
Explanation | You are attempting to install an EBA file but there is an existing asset that has the same symbolic name. |
Action | Either change the symbolic name of the EBA you are installing or uninstall the existing asset. |
Explanation | An enterprise bundle archive (EBA) asset is being added to a composition unit. To set up the web application contained in the EBA, a directory has been assigned to the web application. |
Action | None |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | While attempting to expand the specified EBA file, a required directory could not be created. |
Action | Check that the application server has permission to create the specified directory. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | To complete the expansion of the specified EBA file, a file needs to be renamed. This rename did not succeed. |
Action | Check that the application server has permission to rename the file. |
Explanation | The specified EBA file contains a directory called byValue, or byReference. Neither of these directory names are supported in the root directory of an EBA file. |
Action | Either remove or rename the relevant directory. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | Application bundles cannot provide packages or services to shared bundles. Furthermore, bundles are not allowed to be deployed both as shared and application bundles. Any deployment that requires shared bundles that depend on application bundles is not valid. |
Action | Check that all the invalid shared bundles are needed by the application. If so, ensure that they do not depend on application content. |
Explanation | An attempt was made to import an EBA that contains a deployment manifest file. The processing of this file did not succeed. |
Action | Check that the application server has permission to access the file and check the file is not corrupted. Do not manually edit the deployment manifest. If necessary, remove the deployment manifest from the EBA. This causes a fresh deployment manifest file to be generated when the EBA is imported. |
Explanation | An attempt was made to import an EBA that contains a deployment manifest file. The requirements specified by this file could not be satisfied. |
Action | Check the contents of the deployment manifest file and verify that the system that this EBA is being deployed on is compatible. Check that any required internal or external bundle repositories are configured. Do not manually edit the deployment manifest. If necessary, remove the deployment manifest from the EBA. This causes a fresh deployment manifest file to be generated when the EBA is imported. |
Explanation | The deployment manifest to import does not include all the bundles needed to resolve the enterprise bundle archive (EBA) asset. |
Action | Check that the new deployment manifest, DEPLOYMENT.MF, includes all the bundles that are listed in the exception message. Do not manually edit the deployment manifest. If necessary, remove the deployment manifest from the EBA. This causes a fresh deployment manifest file to be generated when the EBA is imported. |
Explanation | The deployment manifest, DEPLOYMENT.MF, is not compatible with the application manifest, APPLICATION.MF, of the asset. |
Action | Check the new deployment manifest for the following: 1. The Application-SymbolicName and Application-Version in the DEPLOYMENT.MF file must match the corresponding entries in the APPLICATION.MF file. 2. 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. 3. 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.MF file. 4. 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. 5. 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. Do not manually edit the deployment manifest. If necessary, remove the deployment manifest from the EBA. This will cause a fresh deployment manifest file to be generated when the EBA is imported. |
Explanation | The deployment manifest to import includes bundles that are not needed to resolve the enterprise bundle archive (EBA) asset. |
Action | Check that the new deployment manifest, DEPLOYMENT.MF, does not include the bundles that are listed in the exception message. Do not manually edit the deployment manifest. If necessary, remove the deployment manifest from the EBA. This will cause a fresh deployment manifest file to be generated when the EBA is imported. |
Explanation | You attempted to export 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. |
Action | If you did not save changes after you imported the asset, save the changes now. Wait for the bundle download to complete, then try again to export the asset. |
Explanation | There was a problem creating the required pathname during the export of the asset. |
Action | Check that the application server has permission to create this pathname. |
Explanation | There was a problem creating the required pathname during the export of the asset. |
Action | Check that the application server has permission to create this pathname. |
Explanation | The host name of the application server specified on the transport has been resolved as localhost. |
Action | If the web server and application server are on different nodes, investigate why the host name of the application server has been resolved as localhost. |
Explanation | You cannot use the Application-Content header to include composite bundle archives directly in an EBA. |
Action | Remove the composite bundle from the application content. You can either include the individual bundles in the Application-Content or install the composite bundle into a bundle repository for sharing. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | Before you can upgrade the asset deployed within a composition unit, an updated version of the asset must be available and all bundles required by the updated asset must have finished downloading. |
Action | Check that a later version of the asset is available, and that all bundle downloads for the asset have completed. |
Explanation | An exception occurred during the start operation. |
Action | Inspect the server logs prior to this exception for more specific problem diagnostics. |
Explanation | An exception occurred during the stop operation. |
Action | Inspect the server logs prior to this exception for more specific problem diagnostics. |
Explanation | An exception occurred during the update operation. |
Action | Inspect the server logs prior to this exception for more specific problem diagnostics. |
Explanation | The deployment manifest lists specific versions of required bundles. The system cannot resolve these bundle versions. When a deployment manifest is included in an EBA file, the resolver uses only the bundle versions that are specified in the manifest. Other valid bundle versions might be available on the system, but they are not used because they are not specified in the deployment manifest. |
Action | If your application needs to use a deployment manifest, for example to ensure that exactly the same bundle configuration is running in several different environments, use the information given in the exception to identify which bundle versions are required, then make them available to the system. If your application does not need this extra level of control, remove the deployment manifest. Do not manually edit the deployment manifest. |
Explanation | Applications, bundles and composite bundles all share the same namespace, so they must have unique identifiers within the namespace. When validating the application deployment, the runtime environment found a reference to a bundle with the same symbolic name and version as the application. |
Action | Correct the symbolic name of the bundle, composite bundle or application so that there is no longer a clash in the namespace. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | Any specified user must either be a mapped user on the security role or be a member of a mapped group on the security role. The specified user did not meet either of these requirements. |
Action | Either configure the security role to user/group mappings to permit the specified user to act in the specified role, or specify a different user that already has the required permissions. |
Explanation | The specified role has not been configured. |
Action | Configure the specified role. |
Explanation | An incorrect user ID or password has been supplied. |
Action | Retry the action using the correct user ID and password. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | You created or updated a composite bundle archive (CBA) to use as an extension to a composition unit. This extension requires one or more bundles to download from a repository before you can add the extension to the composition unit. |
Action | To start the download process, save your changes to the master configuration. You can view the bundle download status from the composition unit detail panel in the administrative console. Wait for the bundle download to complete, then add the extension to the composition unit. |
Explanation | The given name does not match any existing composition unit name. |
Action | Check the composition unit name. |
Explanation | The invoked operation operates on a composition unit for an OSGi application. The selected composition unit does not contain an OSGi application. |
Action | Check that the selected composition unit is backed by an asset with type aspect "EBA,version=1.0". |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | The application being imported was successfully provisioned against WebSphere Application Server Version 8, but could not be provisioned against the OSGi Applications Feature Pack in WebSphere Application Server Version 7. |
Action | No action is required. However, you can use the information in the resolution error to modify the application so that it can be deployed against the WebSphere Application Server Version 7 OSGi Applications Feature Pack. |
Explanation | The application being imported was successfully provisioned against the WebSphere Application Server Version 7 OSGi Applications Feature Pack, but could not be provisioned against WebSphere Application Server Version 8. |
Action | No action is required. However, this warning indicates that the application might contain an overly strict version requirement. You can use the information in the resolution error to help you modify the application so that it can be deployed against Version 8 nodes. |
Explanation | The application being imported was successfully provisioned against WebSphere Application Server Version 8 and the WebSphere Application Server Version 7 OSGi Applications Feature Pack. However, different results were obtained for the two provisioning operations. You cannot run the same application with different deployments. |
Action | No action is required. |
Explanation | CBAs are supported in Application-Content for WebSphere Application Server Version 8 and later versions. |
Action | No action is required. If the application must run on the WebSphere Application Server Version 7 OSGi Applications Feature Pack, rewrite the application so that there are no CBAs in Application-Content. |
Explanation | All cluster members must be able to run the same applications, but the new cluster member cannot run the named OSGi applications. |
Action | Select another, compatible, node to host the cluster member, or modify the applications so that they can be run using the selected node. |
Explanation | All cluster members must be able to run the same applications, but the new cluster member cannot support OSGi application extensions. |
Action | Select a Version 8 node to host the cluster member, or remove the extension(s) from the application(s) so that they can be run using the selected node. |
Explanation | All cluster members must be able to run the same applications, but the new cluster member cannot support OSGi applications with CBAs in Application-Content. |
Action | Select a Version 8 node to host the cluster member, or modify the application(s) so that they no longer contain CBAs in Application-Content. |
Explanation | All cluster members must be able to run the same applications, but the new cluster member cannot support OSGi applications with Run As Roles defined. |
Action | Select a Version 8 node to host the cluster member, or modify the application(s) configuration so that they no longer define Run As Roles. |
Explanation | Run As Roles can only be configured for WebSphere Application Server Version 8 and later versions. They cannot be configured for a composition unit that is deployed to WebSphere Application Server Version 7 OSGi Applications Feature Pack targets. |
Action | No action is required. If Run As Roles need to be configured then remove any target mappings for WebSphere Application Server Version 7 OSGi Applications Feature Pack nodes. |
Explanation | If a bundle in a Composite Bundle Archive (CBA) uses a package that is not contained in the bundle, or exported by another bundle within the CBA, then the CBA must import the package. |
Action | Correct the composite manifest, COMPOSITEBUNDLE.MF, so that the CBA imports any packages that are used by bundles in the CBA and not otherwise available within the CBA. |
Explanation | The Composite bundle manifest defines a CompositeBundle-ExportService header but no blueprint service declarations match this filter. |
Action | Either add the missing Blueprint service declarations to the CBA contents, or correct the CompositeBundle-ExportService header from the composite manifest, COMPOSITEBUNDLE.MF. |
Explanation | If a bundle in a Composite Bundle Archive (CBA) uses a service that is not contained in the bundle, or exported by another bundle within the CBA, then the CBA must import the service. |
Action | Correct the composite manifest, COMPOSITEBUNDLE.MF, so that the CBA imports any services that are used by bundles in the CBA and not otherwise available within the CBA. |
Explanation | A CBA can only export packages that are exported by the bundles in the CBA. |
Action | Either add the missing export packages to the bundles in the CBA, or remove the details of the unsatisfied exports from the composite manifest, COMPOSITEBUNDLE.MF. |
Explanation | The WAS V7 UpdateAppContentVersionStep command has been replaced with the UpdateAppContentVersions command in WAS V8. Please see the InfoCenter for more information. |
Action | Change the script so as to use the UpdateAppContentVersions command. |
Explanation | The value specified for the Application-ManifestVersion header in APPLICATION.MF is incorrect. |
Action | Correct the value of Application-ManifestVersion in APPLICATION.MF. |
Explanation | It is not possible to update a cba bundle to the requested version as there is already an extension present with the same symbolic name at that version. |
Action | Either remove the extension, or modify the bundle version you are attempting to update to. |
Explanation | Local, "No Interface" and "Local Home" views of an enterprise bean can be bound only into locally acessible JNDI. This means that their binding names must start with "ejblocal:". |
Action | Adjust the binding names for any locally accessible EJB views so that they use the ejblocal: namespace prefix. |
Explanation | The EJB bindings file included in the bundle contains ambiguous mapping configuration information for an EJB interface |
Action | Correct the bindings file so that there is only one configured mapping for each EJB interface. |
Explanation | The EJB bindings file included in the bundle contains invalid mapping configuration for an enterprise bean. |
Action | Correct the bindings file so that there is either a simple mapping name, or specific mapping configuration information, but not both. |
Explanation | An enterprise bundle archive (EBA) that includes message destination references or resource environment references in an EJB module specifies a JNDI name for a message destination reference or resource environment reference that does not exist in the JNDI namespace. |
Action | If the message destination reference or resource environment reference should be in the JNDI namespace, either bind an object to the name, or correct the message destination reference or resource environment reference and update the EBA. |
Explanation | An enterprise bundle archive (EBA) that includes resource references in an EJB module specifies a JNDI name for a resource reference that does not exist in the JNDI namespace. |
Action | 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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | Default bindings must be created for unbound EJB references. No enterprise bean could be found to which to bind this reference. |
Action | Either bind the reference to a known JNDI location, or correct the application. |
Explanation | Default bindings must be created for unbound EJB references. More than one possible enterprise bean was found to which this reference could be bound. |
Action | Either bind the reference to a particular enterprise bean, or correct the application. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | An OSGi application symbolic name cannot contain the string ".."; that is, two consecutive period characters. |
Action | Change the symbolic name of the OSGi application. |
Explanation | The MDB Listener binding ActivationSpec JNDI name has not been configured. |
Action | You must configure an Activation Spec JNDI reference for the MDB. |
Explanation | The specified MDB Listener binding Activation Spec reference JNDI name does not exist. |
Action | If the reference should be in the JNDI namespace, either bind an object to the name, or correct the reference and update the EBA. |
Explanation | The specified MDB listener binding destination reference JNDI name does not exist. |
Action | If the reference should be in the JNDI namespace, either bind an object to the name, or correct the reference and update the EBA. |
Explanation | The specified Auth Alias does not exist, or is not visible to this application. |
Action | Please configure the required Auth Alias, or ensure it is configured in the correct scope for the application. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | The constituent parts of the java:global/application_name/module_name/ejb_name or java:app/module_name/ejb_name lookup references can change after an OSGi application is updated, so that the references must be modified accordingly, which makes this approach impractical. |
Action | Use OSGi services to configure EJB dependencies, or declare an EJB reference and map it to the EJB JNDI name. |
Explanation | The specified exception occurred while modelling the specified bundle. |
Action | Study the specified exception for details of the problem, and fix the issue. |