SUSPECTED_CIRCULAR_DEPENDENCIES=CWSAL0063E: Resolution of asset {0} indicates invalid dependencies of shared content on application content: {1} 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. Check that all the invalid shared bundles are needed by the application. If so, ensure that they do not depend on application content. EXCEPTION_READING_JAR_RESOURCE=CWSAL0006E: Cannot read the bundle manifest for the JAR file {0} in the EBA file {1}. 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. PROVISIONER_SERVICE_UNAVAILABLE=CWSAL0017E: An internal error has occurred. The provisioner service {0} is unavailable. CMSG0001 CMSG0002 APP_START_FAILED=CWSAL0078E: The OSGi application deployed in composition unit {0} in business-level application {1} did not start. An exception occurred during the start operation. Inspect the server logs prior to this exception for more specific problem diagnostics. FORBIDDEN_ROOT_ENTRY=CWSAL0061E: enterprise bundle archive (EBA) file {1} contains directory {0}, which is not supported. 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. Either remove or rename the relevant directory. INVALID_ROLE=CWSAL0040E: The specified role {0} does not exist. 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. DEPLOYMENT_MF_DOES_NOT_MEET_REQS=CWSAL0067E: The deployment manifest to import is not valid for the asset {0} because it does not meet the requirements in the application manifest. The deployment manifest, DEPLOYMENT.MF, is not compatible with the application manifest, APPLICATION.MF, of the asset. 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. UPDATE_RESOLVE_FAILED=CWSAL0031E: The selected bundle versions cannot be resolved or are not compatible. 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. USER_NOT_IN_ROLE=CWSAL0084E: The user {0}, is not a mapped user or a member of a mapped group for role {1}. 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. 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. CBA_IN_APP_CONTENT_MIXED_VERSION=CWSAL0097W: The application {0} contains one or more composite bundle archives (CBAs) {1} in its Application-Content. This is not supported on the WebSphere Application Server Version 7 OSGi Applications Feature Pack. CBAs are supported in Application-Content for WebSphere Application Server Version 8 and later versions. 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. EXCEPTION_READING_APP_MANIFEST=CWSAL0002E: An IOException occurred when reading the application manifest file of the enterprise bundle archive (EBA) {0}. The file might be invalid, corrupted or unreadable. An IOException occurred when reading an enterprise bundle archive (EBA) application manifest file. The file might be invalid, corrupted or unreadable. Check that the application manifest file, APPLICATION.MF, follows the specification for manifest files. INVALID_PLUGIN_CONFIG_FILE_URI=CWSAL0033E: An internal error has occurred. Plugin Config File URI is not the expected format {0}. CMSG0001 CMSG0002 PROVISIONING_WRONG_VERSION_EXCEPTION=CWSAL0016E: An internal error has occurred. An incorrect result was returned during provisioning of the enterprise bundle archive (EBA) file {0}, the maximum version {1} was expected to be the same as the minimum version {2}. CMSG0001 CMSG0002 RESOLUTION_FAILURE_V8_MIXED_VERSION=CWSAL0095W: The application {0} could not be provisioned for all nodes in the cell. The application can only be deployed on Version 7 nodes that are running the OSGi Applications Feature Pack. The resolution error was {1}. 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. 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. ADD_CLUSTER_MEMBER_RUN_AS_ROLE_MIXED_VERSION=CWSAL0101E: A cluster member cannot be created on the node {0} because the OSGi application(s) {1} define Run As Roles. 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. 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. APP_NAME_MATCHES_CONTENT=CWSAL0082E: The deployment manifest for the application {0} at version {1} lists content with the same symbolic name and version as the application. 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. Correct the symbolic name of the bundle, composite bundle or application so that there is no longer a clash in the namespace. INVALID_PACKAGE_REQUIREMENT_ATTRIBUTES=CWSAL0048E: The asset {0} cannot be resolved. The attribute {1} on an import for package {2} cannot be satisfied at deployment. 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. UNABLE_TO_LOCATE_EXPANSION_LOCATION=CWSAL0056E: An internal error occurred. Unable to locate the configuration data needed to expand {0}. CMSG0001 CMSG0002 MODELLER_EXCEPTION_DEPLOYING_BUNDLE=CWSAL0126E: An exception occurred while modelling bundle {0}: {1} The specified exception occurred while modelling the specified bundle. Study the specified exception for details of the problem, and fix the issue. UNABLE_TO_READ_WEB_XML=CWSAL0034E: An internal error has occurred. Unable to get the InputStream for web.xml zip Entry in War {0}. CMSG0001 CMSG0002 INVALID_MDB_LISTENER_AUTHALIAS_REFERENCE=CWSAL0124W: No MDB Listener Auth Alias that matches the name {0} could be found on the target {1} for the resource used by bean {2} in bundle {3} at version {4}. The specified Auth Alias does not exist, or is not visible to this application. Please configure the required Auth Alias, or ensure it is configured in the correct scope for the application. UNSATISFIED_CIRCULAR_SERVICE_DEPENDENCY=CWSAL0044E: The asset {0} cannot be resolved. It requires the bundle {1}, which is not listed in the Application-Content header in the application manifest, APPLICATION.MF. This bundle consumes the service {2} from bundle {3}, which is 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. BUNDLE_DOWNLOAD_REQUESTED=CWSAL0037W: The asset {0} requires external downloads before it can be deployed to a composition unit. 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. 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. COULD_NOT_CONVERT_WAR=CWSAL0010E: Conversion of the WAR file {0} in EBA file {1} to a WAB file did not complete successfully. 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. REPOSITORY_ADMIN_SUPPORT_UNAVAILABLE=CWSAL0076E: An internal error occurred. The RepositoryAdminSupport service is not available from the OSGi service registry. CMSG0001 CMSG0002 ALIAS_IN_INVALID_DOMAIN=CWSAL0024E: Authentication alias {0} does not exist in the security domain {2} of the target {1}. 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. ADD_CLUSTER_MEMBER_CBA_FAILURE_MIXED_VERSION=CWSAL0100E: A cluster member cannot be created on the node {0} because the OSGi application(s) {1} contain composite bundle archives (CBAs) in Application-Content. 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. 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. NOT_AN_EBA_CU=CWSAL0091E: The composition unit {0} does not correspond to an OSGi application. The invoked operation operates on a composition unit for an OSGi application. The selected composition unit does not contain an OSGi application. Check that the selected composition unit is backed by an asset with type aspect "EBA,version=1.0". DEPLOYMENT_MANIFEST_MISSING=CWSAL0032E: An internal error occurred. Could not extract the deployment manifest from the asset binary {0}. CMSG0001 CMSG0002 MODELLED_RESOURCE_MANAGER_UNAVAILABLE=CWSAL0074E: An internal error occurred. The ModelledResourceManager service is not available from the OSGi service registry. CMSG0001 CMSG0002 CBA_BUNDLE_ASSET_NOT_SUPPORTED=CWSAL0125E: An internal error occurred. The CBA bundle {0} at version {1} cannot be modelled. CMSG0001 CMSG0002 NO_APPLICATION_XML=CWSAL0008W: The Java EE application descriptor file was not found in EBA file {0}. Without this descriptor file, context roots for WAR files are set to default values. 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. UNABLE_TO_OPEN_DEPLOYMENT_MANIFEST=CWSAL0064E: Unable to process the deployment manifest file that was provided by the application from this location {0}. An attempt was made to import an EBA that contains a deployment manifest file. The processing of this file did not succeed. 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. SERVICE_UNAVAILABLE=CWSAL0093E: An internal error occurred. The {0} service is not available from the OSGi service registry. CMSG0001 CMSG0002 AJPS_COULD_NOT_CREATE_DIR=CWSAL0030E: Cannot create the directory {0}. The specified directory cannot be created. Check that storage space exists, and that the product has the necessary permissions to create the directory. INVALID_MODULE_TYPE=CWSAL0115E: An internal error occurred. The module {0} was of an unexpected type. CMSG0001 CMSG0002 ERRORS_DURING_TRANSFORMATION=CWSAL0014E: EBA file {0} installed with errors. The validation and installation of the enterprise bundle archive (EBA) file completed with errors. See the accompanying error messages in the SystemOut.log file for further information. EJB_DEFAULT_BINDING_IMPOSSIBLE=CWSAL0116E: No default binding could be created for EJB reference {0} in bundle {1} at version {2} with interface {3} since no matching enterprise beans exist in the application. Default bindings must be created for unbound EJB references. No enterprise bean could be found to which to bind this reference. Either bind the reference to a known JNDI location, or correct the application. ENV_ENTRY_BAD_VALUE=CWSAL0130E: Environment entry {0} for EJB {1} in bundle with name {2} and version {3} has invalid value {4} for type {5}. The value specified for the indicated environment entry is not valid. Specify a valid value for the indicated environment entry. ASSET_IN_NOT_FOUND=CWSAL0083E: An internal error has occurred. Cannot find the config asset object for asset {0}. CMSG0001 CMSG0002 ENV_ENTRY_BAD_EMPTY_STRING_VALUE=CWSAL0131E: Environment entry {0} for EJB {1} in bundle with name {2} and version {3} has invalid empty string value for type {4}. The value specified for the indicated environment entry is not valid. Specify a valid value for the indicated environment entry. NO_EJB_RESOURCE_REFERENCE=CWSAL0114E: Cannot find the resource reference with JNDI name {0} and type {1} on the target {2} for the EJB resource reference {3} defined in bundle {4} with version {5}. 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. 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. APP_STOP_FAILED=CWSAL0079E: The OSGi application deployed in composition unit {0} in business-level application {1} did not stop. An exception occurred during the stop operation. Inspect the server logs prior to this exception for more specific problem diagnostics. INVALID_RUNAS_ROLE=CWSAL0085E: The role {0}, is not a valid role. The specified role has not been configured. Configure the specified role. UNAUGMENTED_CLUSTER_MEMBER=CWSAL0052E: The cluster member {0} is not augmented with the features, {2}, required by the OSGi application {1}. 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. Check that the proposed member of the cluster has all the required features for the OSGi application listed in the error message. BPRRBS_COULD_NOT_CREATE_DIR=CWSAL0028E: Cannot create the directory {0}. The specified directory cannot be created. Check that storage space exists, and that the product has the necessary permissions to create the directory. DEPLOYMENT_MF_CONTAINS_REDUNDANCY=CWSAL0068E: The deployment manifest content is not correct. The following bundles are redundant: {0}. The deployment manifest to import includes bundles that are not needed to resolve the enterprise bundle archive (EBA) asset. 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. INVALID_GROUP=CWSAL0042E: The specified group {0} is not valid. Attempted to map a security role to a group that is not valid. Check that the specified group exists. ENV_ENTRY_NO_VALUE_OR_LOOKUP_NAME=CWSAL0128E: Environment entry {0} for EJB {1} in bundle with name {2} and version {3} does not have a value or lookup-name specified. Either a value or a lookup-name for the indicated environment entry must be specified. Specify a value or lookup-name for the indicated environment entry. UNABLE_TO_LOOKUP_ADMIN_SERVICE=CWSAL0088E: An internal error has occurred. The Admin Service has not been registered. CMSG0001 CMSG0002 CU_BUNDLE_DOWNLOAD_REQUESTED=CWSAL0089W: An extension to the composition unit {0} requires external downloads. 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. 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. NO_SERVERS_AVAIL=CWSAL0049E: None of the servers or clusters has the required feature {0} deployed for the asset {1}. The required feature could not be found on any of the servers. Install the required feature on at least one of the servers. MISSING_BUNDLES=CWSAL0026E: An internal error has occurred. The enterprise bundle archive (EBA) file {0} is missing the following bundles: {1}. CMSG0001 CMSG0002 MULTIPLE_CUS_WITH_THE_SAME_ASSET=CWSAL0039E: Cannot add the asset {0} to this business-level application because it is already added to the business level application: {1} 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. RESOLUTION_INCONSISTENT_MIXED_VERSION=CWSAL0096W: Provisioning the application {0} produced different results for WebSphere Application Server Version 8 and the WebSphere Application Server Version 7 OSGi Applications Feature Pack. The Version 8 result will be used. 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. No action is required. NEW_DIRECTORY_MAPPING=CWSAL0054I: {1} has been assigned to the directory {0}. 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. None NO_APPLICATION_MANIFEST_DURING_RESOLVE=CWSAL0004E: An internal error has occurred. Cannot read the application manifest or deployment manifest for the enterprise bundle archive (EBA) file {0}. CMSG0001 CMSG0002 STEP_NOT_FOUND=CWSAL0020E: An internal error has occurred. The step {0} cannot be found. CMSG0001 CMSG0002 UNCONVERTIBLE_JAR_FILE=CWSAL0038W: The asset {0} contains a JAR file {1} that is not a bundle and that will not be converted. If other parts of the application depend on this file, the application will fail at run time. 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). NO_APPLICATION_MANIFEST_DURING_DETAILS=CWSAL0005E: An internal error has occurred. Cannot read the application manifest or deployment manifest for the enterprise bundle archive (EBA) file {0}. CMSG0001 CMSG0002 EJB_MAPPING_NAMESPACE_ERROR=CWSAL0110E: The EJB interface {0} for enterprise bean {1} in Bundle {2} at version {3} cannot be bound to the location {4}. Locally accessible EJB interfaces must be bound into the ejblocal: namespace. 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:". Adjust the binding names for any locally accessible EJB views so that they use the ejblocal: namespace prefix. NO_APPLICABLE_UPDATES_AVAILABLE=CWSAL0077E: The CompUnitStatusStep indicates that the composition unit {0} should be upgraded to the latest deployment version available from asset {1}. However, the composition unit {0} is up-to-date. 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. Check that a later version of the asset is available, and that all bundle downloads for the asset have completed. UNABLE_TO_OBTAIN_CU=CWSAL0055E: An internal error occurred. Unable to obtain composition unit for asset {0}. CMSG0001 CMSG0002 ADD_CLUSTER_MEMBER_EXTENSION_FAILURE_MIXED_VERSION=CWSAL0099E: A cluster member cannot be created on the node {0} because the OSGi application(s) {1} have been extended. All cluster members must be able to run the same applications, but the new cluster member cannot support OSGi application extensions. 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. UPDATE_EXTENSION_CONFLICT=CWSAL0109E: The bundle {0} in Composition Unit {1} could not be updated as there is a conflicting extension with the same symbolic name. 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. Either remove the extension, or modify the bundle version you are attempting to update to. ENV_ENTRY_BAD_TYPE=CWSAL0129E: Environment entry {0} for EJB {1} in bundle with name {2} and version {3} has invalid type {4}. The type specified for the indicated environment entry is not valid. Specify a valid type for the indicated environment entry. INVALID_MDB_ACTSPEC_REFERENCE=CWSAL0121W: No MDB Activation Spec that matches the JNDI name {0} could be found on the target {1} for the resource used by bean {2} in bundle {3} at version {4}. The specified MDB Listener binding Activation Spec reference JNDI name does not exist. If the reference should be in the JNDI namespace, either bind an object to the name, or correct the reference and update the EBA. UNABLE_TO_LOCATE_TYPE=CWSAL0092E: An internal error occurred. The asset {0} could not be queried for content. CMSG0001 CMSG0002 CBA_IN_APPLICATION_CONTENT=CWSAL0073E: The application {0} includes a composite bundle {1} in its application content. This is not supported. You cannot use the Application-Content header to include composite bundle archives directly in an EBA. 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. INCORRECT_BUNDLE_IN_CACHE=CWSAL0027E: An internal error has occurred. A file with the correct name exists in the bundle cache, but it does not contain the expected bundle {0}/{1}. CMSG0001 CMSG0002 NO_EJB_MSG_DEST_REFERENCE=CWSAL0113E: Cannot find the message destination reference or resource environment reference with JNDI name {0} and type {1} on the target {2} for the EJB message destination reference or resource environment reference {3} defined in bundle {4} with version {5}. 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. 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. DOTDOT_ILLEGAL_IN_APP_NAME=CWSAL0119E: The OSGi application {0} is not valid because its symbolic name contains two consecutive period characters. An OSGi application symbolic name cannot contain the string ".."; that is, two consecutive period characters. Change the symbolic name of the OSGi application. EXCEPTION_READING_ZIP=CWSAL0007E: Cannot read the EBA file {0}. 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. UNABLE_TO_LOOKUP_ADMIN_MBEAN=CWSAL0087E: An internal error has occurred. The SecurityAdmin MBean has not been registered. CMSG0001 CMSG0002 CBA_WITH_MISSING_SERVICE_IMPORTS=CWSAL0105W: Service references in the contents of the Composite Bundle Archive (CBA) {0} cannot be resolved. If these services are provided by bundles that are not included in the CBA, then the CBA must import them. The following service dependencies were unresolved: {1} 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. 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. EXCEPTION_WHILE_WRITING_EBA=CWSAL0001E: Cannot write the migrated EBA file {0}. 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. RESOLUTION_FAILURE_FEP_MIXED_VERSION=CWSAL0094W: The application {0} could not be provisioned for all nodes in the cell. The application can only be deployed on Version 8 nodes. The resolution error was {1}. 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. 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. USING_LOCALHOST_AS_HOST_NAME=CWSAL0072W: Using localhost as the host name for the transport for the server {0}.{1}. Request routing will work as long as the web server and application server are on the same node. The host name of the application server specified on the transport has been resolved as localhost. 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. SYMBOLIC_NAME_ALREADY_IN_USE=CWSAL0053E: The EBA file {0} cannot be installed. The Application-SymbolicName {1} of the EBA is already being used by the asset {2}. You are attempting to install an EBA file but there is an existing asset that has the same symbolic name. Either change the symbolic name of the EBA you are installing or uninstall the existing asset. ADD_CLUSTER_MEMBER_PROVISIONING_FAILURE_MIXED_VERSION=CWSAL0098E: A cluster member cannot be created on the node {0} because the OSGi application(s) {1} cannot be provisioned against it. The resolution error was {2}. All cluster members must be able to run the same applications, but the new cluster member cannot run the named OSGi applications. Select another, compatible, node to host the cluster member, or modify the applications so that they can be run using the selected node. SECURITY_PERMISSIONS_PARSEREXCEPTION=CWSAL0047E: Cannot parse the file {0} for the enterprise bundle archive (EBA) file {1}. The specified file could not be parsed. Check that the file is formatted correctly and not corrupted. NO_APPLICATION_MANIFEST_DURING_UPDATE=CWSAL0003E: An internal error has occurred. Cannot read the application manifest or deployment manifest for the enterprise bundle archive (EBA) file {0}. CMSG0001 CMSG0002 UNABLE_TO_CREATE_FILE=CWSAL0071E: Unable to create file: {0} There was a problem creating the required pathname during the export of the asset. Check that the application server has permission to create this pathname. UPDATE_APP_CONTENT_VERSION_STEP_CHANGED=CWSAL0107E: The UpdateAppContentVersionStep command in WAS V7 has been replaced with the UpdateAppContentVersions command in WAS V8. The WAS V7 UpdateAppContentVersionStep command has been replaced with the UpdateAppContentVersions command in WAS V8. Please see the InfoCenter for more information. Change the script so as to use the UpdateAppContentVersions command. EMPTY_DEPLOYMENT_CONTENT=CWSAL0013E: An internal error has occurred. The enterprise bundle archive (EBA) file {0}, when resolved, has no content that can be deployed. CMSG0001 CMSG0002 PROVISIONING_EXCEPTION=CWSAL0015E: Cannot resolve EBA file. Exception: {0}. 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. RESOLVER_SERVICE_UNAVAILABLE=CWSAL0018E: An internal error has occurred. Cannot resolve the enterprise bundle archive (EBA) file {0} because the service {1} is unavailable. CMSG0001 CMSG0002 INVALID_USER=CWSAL0041E: The specified user {0} is not valid. Attempted to map a security role to a user that is not valid. Check that the specified user exists. NO_BUNDLECACHEMANAGER_FOUND=CWSAL0062E: An internal error occurred. Failed to find an MBean for the BundleCacheManager for profile {0}. CMSG0001 CMSG0002 JAVAGLOBAL_JAVAAPP_WARNING=CWSAL0125W: The binding {0} for EJB reference {1} in bundle {2} at version {3} with interface {4} might cause the application to function incorrectly after an update. 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. Use OSGi services to configure EJB dependencies, or declare an EJB reference and map it to the EJB JNDI name. UNABLE_TO_EXPAND_EBA_CANNOT_CREATE_DIRECTORY=CWSAL0057E: Unable to expand enterprise bundle archive (EBA) file {0}, cannot create directory {1}. While attempting to expand the specified EBA file, a required directory could not be created. Check that the application server has permission to create the specified directory. INCOMPATIBLE_PACKAGE_VERSION_REQUIREMENTS=CWSAL0045E: The asset {0} cannot be resolved. It has incompatible version requirements on the following packages: {1}. 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. RUN_AS_ROLE_MIXED_VERSION=CWSAL0102W: Run As Roles cannot be configured for nodes prior to WebSphere Application Server Version 8. Any configuration will be ignored. 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. 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. INVALID_USERID_OR_PASSWD=CWSAL0086E: The user ID or password is incorrect. An incorrect user ID or password has been supplied. Retry the action using the correct user ID and password. APP_UPDATE_FAILED=CWSAL0080E: The update operation did not succeed for the OSGi application deployed in composition unit {0} in business-level application {1}. An exception occurred during the update operation. Inspect the server logs prior to this exception for more specific problem diagnostics. APPLICATION_CONTENT_EMPTY=CWSAL0019E: An internal error occurred. The Application-Content entry of the application manifest in the enterprise bundle archive (EBA) file {0} is empty, so no bundle will be installed. CMSG0001 CMSG0002 EXCEPTION_READING_APPLICATION_XML=CWSAL0009E: Cannot read the Java EE application descriptor file in EBA file {0}. 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. NO_RESOURCE_REFERENCE=CWSAL0035E: Cannot find the resource reference with JNDI name {0} and type {1} on the target {2} for the web module resource reference {3} defined in bundle {4} with version {5}. 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. EJB_DEFAULT_BINDING_AMBIGUOUS=CWSAL0117E: No default binding could be created for EJB reference {0} in bundle {1} at version {2} with interface {3} becuase there are two or more possible bindings. The reference could be bound to any of the following enterprise beans: {4}. Default bindings must be created for unbound EJB references. More than one possible enterprise bean was found to which this reference could be bound. Either bind the reference to a particular enterprise bean, or correct the application. AUTH_ALIAS_SET_FOR_APPLICATION_AUTHTYPE=CWSAL0025E: Authentication alias {0} is configured incorrectly. It is not applicable to bind an alias with an authentication type of Application to references. Authentication aliases with an authentication type of Application cannot be bound to Blueprint resource references. Remove the authentication alias from the relevant resource reference. INVALID_VIRTUAL_HOST=CWSAL0021E: The virtual host {0} specified for bundle {1} does not exist. Attempted to map a web application bundle (WAB) to a virtual host that is not valid. Check that the specified virtual host exists. APP_CONTENT_USE_BUNDLE_DUPLICATE=CWSAL0046E: The EBA file {0} application manifest lists bundles in the Application-Content header that are also listed in the Use-Bundle header. 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. ENV_ENTRY_NO_TYPE=CWSAL0127E: Environment entry {0} for EJB {1} in bundle with name {2} and version {3} does not have a type. The indicated environment entry does not specify a type. A type is required when no injection targets are specified. Specify a type or injection targets for the indicated environment entry. CBA_WITH_MISSING_PACKAGE_IMPORTS=CWSAL0103E: The Composite Bundle Archive (CBA) {0} is not valid. Packages imported by bundles in the CBA are missing from the Import-Package header of the CBA manifest file. The following problems were reported: {1} 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. 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. EJB_DUPLICATE_MAPPING_ERROR=CWSAL0111E: The enterprise bean {0} in bundle {1} at version {2} has multiple mappings for the interface {3} in its bindings file. The mappings were {4} and {5}. The EJB bindings file included in the bundle contains ambiguous mapping configuration information for an EJB interface Correct the bindings file so that there is only one configured mapping for each EJB interface. NO_SUCH_CU=CWSAL0090E: No composition unit with name {0} can be found in the current cell. The given name does not match any existing composition unit name. Check the composition unit name. EXTENSION_LIST_NOT_SUPPORTED=CWSAL0050W: The EBA file {0} contains a MANIFEST.MF with the Extension-List header. Conversion of this header is not supported. 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. UNSATISFIED_CIRCULAR_PACKAGE_DEPENDENCY=CWSAL0043E: The asset {0} cannot be resolved. It requires the bundle {1}, which is not listed in the Application-Content header in the application manifest, APPLICATION.MF. This bundle imports the package {2} from bundle {3}, which is listed in the Application-Content header. 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. EJB_REF_STEP_NO_MAPPINGS=CWSAL0118E: EJBRefStep.validateTable(): EJBMappingsStep has not run, and should have done. CMSG0001 CMSG0002 MORE_THAN_ONE_SECURITY_DOMAIN=CWSAL0036E: The asset {0} cannot be deployed to both target {1} in security domain {2} and target{3} in security domain {4}. 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. CBA_WITH_EXTRA_SERVICE_EXPORTS=CWSAL0104W: The composite manifest of Composite Bundle Archive (CBA) {0} contains a CompositeBundle-ExportService header but no services defined in the CBA match this filter. The Composite bundle manifest defines a CompositeBundle-ExportService header but no blueprint service declarations match this filter. Either add the missing Blueprint service declarations to the CBA contents, or correct the CompositeBundle-ExportService header from the composite manifest, COMPOSITEBUNDLE.MF. EJB_SIMPLE_NAME_AND_MAPPING_ERROR=CWSAL0112E: The enterprise bean {0} in bundle {1} at version {2} has a simple mapping name defined, but also has specific mappings in its bindings file. The EJB bindings file included in the bundle contains invalid mapping configuration for an enterprise bean. Correct the bindings file so that there is either a simple mapping name, or specific mapping configuration information, but not both. UNABLE_TO_EXPAND_EBA_CANNOT_DELETE_LAST_DIRECTORY=CWSAL0059E: An internal error occurred. Unable to delete leaf directory of {0} so that a directory rename can proceed. CMSG0001 CMSG0002 UNABLE_TO_EXPAND_EBA_NO_EXPANSION_DIRECTORY=CWSAL0058E: An internal error occurred. Unable to expand enterprise bundle archive (EBA), no expansion directory specified in the configuration for {0}. CMSG0001 CMSG0002 UPDATE_ASSET_NOT_SUPPORTED=CWSAL0051E: An attempt has been made to update an OSGi application asset. This is not supported. Update of OSGi application assets can be performed using the "Update bundle versions in this application" panel from the OSGi application asset configuration page. The update of an OSGi application asset with a new binary is not supported. 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. NO_MDB_ACTSPEC_REFERENCE=CWSAL0120W: No MDB Activation Spec JNDI name has been configured for bean {0} in bundle {1} at version {2}, on target {3}. The MDB Listener binding ActivationSpec JNDI name has not been configured. You must configure an Activation Spec JNDI reference for the MDB. UNABLE_TO_RENAME=CWSAL0060E: Unable to rename the file {0} to {1} as part of the expansion of enterprise bundle archive (EBA) file {2}. To complete the expansion of the specified EBA file, a file needs to be renamed. This rename did not succeed. Check that the application server has permission to rename the file. CBA_WITH_IMPOSSIBLE_PACKAGE_EXPORTS=CWSAL0106E: The Composite Bundle Archive (CBA), {0} is not valid. The following exported packages listed in the composite manifest are not exported by bundles in the CBA: {1} A CBA can only export packages that are exported by the bundles in the CBA. 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. BUNDLE_DEPENDENCIES_UNAVAILABLE=CWSAL0022E: Cannot add asset {0} because bundles that it requires are not downloaded. To start the bundle download, save changes to the master configuration after importing the asset. 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. DEPLOYMENT_MF_INCORRECT=CWSAL0066E: The deployment manifest content is not correct. The following extra bundles are required {0}. The deployment manifest to import does not include all the bundles needed to resolve the enterprise bundle archive (EBA) asset. 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. ECES_COULD_NOT_CREATE_DIR=CWSAL0029E: Cannot create the directory {0}. The specified directory cannot be created. Check that storage space exists, and that the product has the necessary permissions to create the directory. ASSET_BUNDLES_UNAVAILABLE=CWSAL0069E: Cannot export asset {0} because bundle {1} that it requires is not fully downloaded. 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. 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. DEPLOYMENT_MANIFEST_MANAGER_UNAVAILABLE=CWSAL0075E: An internal error occurred. The DeploymentManifestManager service is not available from the OSGi service registry. CMSG0001 CMSG0002 PROVISIONING_EXCEPTION_WITH_DEP_MF=CWSAL0081E: Cannot resolve EBA file. The included deployment manifest is not valid on this system. Exception: {0}. 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. 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. INCOMPATIBLE_APP_MF_VERSION=CWSAL0108E: The value specified for the application manifest version {0} is not supported. The supported version is {1}. The value specified for the Application-ManifestVersion header in APPLICATION.MF is incorrect. Correct the value of Application-ManifestVersion in APPLICATION.MF. DEPLOYMENT_MF_INCOMPATIBLE=CWSAL0065E: The requirements specified by the deployment manifest within the EBA cannot be satisfied. The exception generated is {0}. An attempt was made to import an EBA that contains a deployment manifest file. The requirements specified by this file could not be satisfied. 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. EMPTY_APPLICATION_CONTENT=CWSAL0012E: The EBA file {0} specifies Application-Content in its application manifest, but the entry is empty. 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. INVALID_MDB_DESTINATION_REFERENCE=CWSAL0123W: No MDB Destination that matches the JNDI name {0} could be found on the target {1} for the resource used by bean {2} in bundle {3} at version {4}. The specified MDB listener binding destination reference JNDI name does not exist. If the reference should be in the JNDI namespace, either bind an object to the name, or correct the reference and update the EBA. NO_APPLICATION_CONTENT=CWSAL0011E: The EBA file {0} does not specify Application-Content, and contains no valid bundles. 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). UNABLE_TO_CREATE_PATH=CWSAL0070E: Unable to create directory: {0} There was a problem creating the required pathname during the export of the asset. Check that the application server has permission to create this pathname.