WebSphere Komunikaty serwera aplikacji
             Systemy operacyjne: AIX, HP-UX, Linux, Solaris, System Windows, z/OS


CWSAL

CWSAL0001E: Cannot write the migrated EBA file {0}.
Objaśnienie An IOException occurred when writing a migrated enterprise bundle archive (EBA) file.
Działanie Check that the product has the necessary permissions to write to the relevant directory, that the target file is not locked, and that storage space is available.
CWSAL0002E: Cannot read the migrated EBA file {0}.
Objaśnienie An IOException occurred when reading an enterprise bundle archive (EBA) application manifest file. The file might be corrupt or unreadable.
Działanie Check that the application manifest file, APPLICATION.MF, is not damaged or unreadable.
CWSAL0003E: An internal error has occurred. Cannot read the application manifest or deployment manifest for the enterprise bundle archive (EBA) file {0}.
Objaśnienie This exception is unexpected. The cause is not immediately known.
Działanie If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CWSAL0004E: An internal error has occurred. Cannot read the application manifest or deployment manifest for the enterprise bundle archive (EBA) file {0}.
Objaśnienie This exception is unexpected. The cause is not immediately known.
Działanie If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CWSAL0005E: An internal error has occurred. Cannot read the application manifest or deployment manifest for the enterprise bundle archive (EBA) file {0}.
Objaśnienie This exception is unexpected. The cause is not immediately known.
Działanie If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CWSAL0006E: Cannot read the bundle manifest for the JAR file {0} in the EBA file {1}.
Objaśnienie An IOException occurred when locating the manifest of a JAR file in an enterprise bundle archive (EBA) file. The file might be corrupt or unreadable.
Działanie Check that the file has the appropriate permissions and that it is in the correct format.
CWSAL0007E: Cannot read the EBA file {0}.
Objaśnienie An IOException occurred when reading an enterprise bundle archive (EBA) file. The file might be corrupt or unreadable.
Działanie Check that the file has the appropriate permissions and that it is in the correct format.
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.
Objaśnienie The system processed a Web application archive (WAR) without an associated application descriptor file, application.xml, which defines context roots. Context roots for the migrated WAR file will be set to default values.
Działanie If an application descriptor file is required, check that it is provided and correctly packaged into the enterprise bundle archive (EBA) file.
CWSAL0009E: Cannot read the Java EE application descriptor file in EBA file {0}.
Objaśnienie An IOException occurred when reading the Java EE application descriptor file in an enterprise bundle archive (EBA) file.
Działanie Check that the application descriptor file is not corrupted, that it is readable and that it has appropriate permissions set.
CWSAL0010E: Conversion of the WAR file {0} in EBA file {1} to a WAB file did not complete successfully.
Objaśnienie Web application archive (WAR) files in an enterprise bundle archive (EBA) must be converted to Web application bundles (WABs) before they can be deployed. The conversion process did not complete successfully.
Działanie Check that the WAR file is valid.
CWSAL0011E: The EBA file {0} does not specify Application-Content, and contains no valid bundles.
Objaśnienie An enterprise bundle archive (EBA) file must contain at least one valid OSGi bundle or Web application archive (WAR) file, or list at least one OSGi bundle in the Application-Content header of its application manifest file.
Działanie Modify the EBA file to contain at least one valid bundle or WAR (included by value) or list at least one bundle in the in the Application-Content header of its application manifest file, application.mf (included by reference).
CWSAL0012E: The EBA file {0} specifies Application-Content in its application manifest, but the entry is empty.
Objaśnienie An enterprise bundle archive (EBA) file contains an empty Application-Content header in its application manifest, application.mf. If provided, this entry must list at least one valid bundle.
Działanie Modify the Application-Content header in the application.mf file.
CWSAL0013E: An internal error has occurred. The enterprise bundle archive (EBA) file {0}, when resolved, has no content that can be deployed.
Objaśnienie This exception is unexpected. The cause is not immediately known.
Działanie If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CWSAL0014E: EBA file {0} migrated with errors.
Objaśnienie The validation and migration of the enterprise bundle archive (EBA) file completed with errors.
Działanie See the accompanying error messages in the SystemOut.log file for further information.
CWSAL0015E: Cannot resolve EBA file. Exception: {0}.
Objaśnienie The system cannot resolve the locations of the constituent application bundles, at appropriate versions, of the enterprise bundle archive (EBA) file.
Działanie See the exception for further information.
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}.
Objaśnienie This exception is unexpected. The cause is not immediately known.
Działanie If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CWSAL0017E: An internal error has occurred. The provisioner service {0} is unavailable.
Objaśnienie This exception is unexpected. The cause is not immediately known.
Działanie If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CWSAL0018E: An internal error has occurred. Cannot resolve the enterprise bundle archive (EBA) file {0} because the service {1} is unavailable.
Objaśnienie This exception is unexpected. The cause is not immediately known.
Działanie If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
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.
Objaśnienie This exception is unexpected. The cause is not immediately known.
Działanie If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CWSAL0020E: An internal error has occurred. The step {0} cannot be found.
Objaśnienie This exception is unexpected. The cause is not immediately known.
Działanie If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CWSAL0021E: The virtual host {0} specified for bundle {1} does not exist.
Objaśnienie Attempted to map a Web application bundle (WAB) to a virtual host that is not valid.
Działanie Check that the specified virtual host exists.
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.
Objaśnienie You attempted to add an asset that requires one or more bundles to be downloaded from a repository. Either the download has not started, or it is not yet complete.
Działanie If you did not saved changes after you imported the asset, save the changes now. Wait for the bundle download to complete, then try again to add the asset to the business-level application (BLA). You can view the bundle download status of the asset from the asset detail panel in the administrative console.
CWSAL0024E: Authentication alias {0} does not exist in the security domain {2} of the target {1}.
Objaśnienie An authentication alias must exist in the global or target security domain when Blueprint resource references are bound.
Działanie Select an authentication alias that exists in the global or target security domain, or create a suitable authentication alias.
CWSAL0025E: Authentication alias {0} is configured incorrectly. It is not applicable to bind an alias with an authentication type of Application to references.
Objaśnienie Authentication aliases with an authentication type of Application cannot be bound to Blueprint resource references.
Działanie Remove the authentication alias from the relevant resource reference.
CWSAL0026E: An internal error has occurred. The enterprise bundle archive (EBA) file {0} is missing the following bundles: {1}.
Objaśnienie This exception is unexpected. The cause is not immediately known.
Działanie If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
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}.
Objaśnienie This exception is unexpected. The cause is not immediately known.
Działanie If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CWSAL0028E: Cannot create the directory {0}.
Objaśnienie The specified directory cannot be created.
Działanie Check that storage space exists, and that the product has the necessary permissions to create the directory.
CWSAL0029E: Cannot create the directory {0}.
Objaśnienie The specified directory cannot be created.
Działanie Check that storage space exists, and that the product has the necessary permissions to create the directory.
CWSAL0030E: Cannot create the directory {0}.
Objaśnienie The specified directory cannot be created.
Działanie Check that storage space exists, and that the product has the necessary permissions to create the directory.
CWSAL0031E: The selected bundle versions cannot be resolved or are not compatible.
Objaśnienie The system cannot resolve the selected bundle versions. The bundles might have missing dependencies, be incompatible, or not exist.
Działanie Modify the selected set of input bundles and try again. You can use the administrative console to view or preview the status of the asset.
CWSAL0032E: An internal error occurred. Could not extract the deployment manifest from the asset binary {0}.
Objaśnienie This exception is unexpected. The cause is not immediately known.
Działanie If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CWSAL0033E: An internal error has occurred. Plugin Config File URI is not the expected format {0}.
Objaśnienie This exception is unexpected. The cause is not immediately known.
Działanie If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CWSAL0034E: An internal error has occurred. Unable to get the InputStream for web.xml zip Entry in War {0}.
Objaśnienie This exception is unexpected. The cause is not immediately known.
Działanie If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
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}.
Objaśnienie An enterprise bundle archive (EBA) that includes resource references in a Web application archive (WAR) specifies a JNDI name for a resource reference that does not exist in the JNDI namespace.
Działanie If the resource reference should be in the JNDI namespace, either bind an object to the name, or correct the resource reference and update the EBA.
CWSAL0036E: The asset {0} cannot be deployed to both target {1} in security domain {2} and target{3} in security domain {4}.
Objaśnienie To deploy an asset onto more than one target, all targets must be in the same security domain.
Działanie Change the deployment targets to choose a set that are in a single security domain.
CWSAL0037W: The asset {0} requires external downloads. After the asset import completes, save your changes, then wait for the download to complete before you add the asset to a BLA.
Objaśnienie You imported an asset that requires one or more bundles to download from a repository before you can add the asset to business-level application (BLA). To start the download process, save your changes to the master configuration.
Działanie After the asset import completes, save your changes, wait for the bundle download to complete, then add the asset to the BLA. You can view the bundle download status of the asset from the asset detail panel in the administrative console.
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.
Objaśnienie Conversion of utility Java archive (JAR) files and Enterprise JavaBeans (EJB) JAR files is not supported.
Działanie Check that no bundle or Web application bundle (WAB) depends on classes from the JAR file. To avoid the warning message, remove the JAR file from the enterprise bundle archive (EBA).
CWSAL0039E: Cannot add the asset {0} to this business-level application because it is already added to the business level application: {1}
Objaśnienie An enterprise bundle archive (EBA) asset can be in only a single business-level application (BLA).
Działanie Create a new application with the same content but with a different application symbolic name. Import the new application as an EBA asset, then add it to this BLA.
CWSAL0040E: The specified role {0} does not exist.
Objaśnienie Attempted to map users or groups to a security role that does not exist.
Działanie Check that the specified security role exists, or create the role in the application.
CWSAL0041E: The specified user {0} is not valid.
Objaśnienie Attempted to map a security role to a user that is not valid.
Działanie Check that the specified user exists.
CWSAL0042E: The specified group {0} is not valid.
Objaśnienie Attempted to map a security role to a group that is not valid.
Działanie Check that the specified group exists.
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.
Objaśnienie The application is not correctly configured. A shared bundle cannot import a package from an isolated bundle. Bundles that are listed in the Application-Content header are isolated and can provide packages only to other bundles listed in that header.
Działanie Change the packaging or configuration of the application so that bundles that are listed in the Use-Bundle header, or added by the resolver, do not require packages from bundles that are listed in the Application-Content header.
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.
Objaśnienie The application is not correctly configured. A shared bundle cannot consume a service from an isolated bundle. Bundles that are listed in the Application-Content header are isolated and can export services only to other applications through the Application-ExportService mechanism.
Działanie Change the packaging or configuration of the application so that bundles that are listed in the Use-Bundle header, or added by the resolver, do not require services that are provided by bundles that are listed in the Application-Content header.
CWSAL0045E: The asset {0} cannot be resolved. It has incompatible version requirements on the following packages: {1}.
Objaśnienie For bundles that are listed in the Application-Content header in APPLICATION.MF, all imports for a given package must have compatible version requirements.
Działanie Change the packaging or configuration of the application so that all bundles that are listed in the Application-Content header have compatible package version requirements.
CWSAL0046E: The EBA file {0} application manifest lists bundles in the Application-Content header that are also listed in the Use-Bundle header.
Objaśnienie Bundle names that are listed in the Application-Content header of APPLICATION.MF cannot also be listed in the Use-Bundle header, regardless of bundle versions.
Działanie Change the packaging of the Enterprise Bundle Archive (EBA) so that bundle names are not duplicated in the Application-Content and Use-Bundle headers.
CWSAL0047E: Cannot parse the file {0} for the enterprise bundle archive (EBA) file {1}.
Objaśnienie The specified file could not be parsed.
Działanie Check that the file is formatted correctly and not corrupted.
CWSAL0048E: The asset {0} cannot be resolved. The attribute {1} on an import for package {2} cannot be satisfied at deployment.
Objaśnienie For bundles listed in the Application-Content header in APPLICATION.MF, all package imports must have attributes that can be satisfied at deployment.
Działanie Change the packaging or configuration of the application so that all bundles that are listed in the Application-Content header have package imports that can be satisfied at deployment.
CWSAL0049E: None of the servers or clusters has the required feature {0} deployed for the asset {1}.
Objaśnienie The required feature could not be found on any of the servers.
Działanie Install the required feature on at least one of the servers.
CWSAL0050W: The EBA file {0} contains a MANIFEST.MF with the Extension-List header. Conversion of this header is not supported.
Objaśnienie You attempted to convert an enterprise archive (EAR) file to an enterprise bundle archive (EBA) file when the EAR contains a MANIFEST.MF with an Extension-List header, but conversion of this header is not supported. An EAR file uses the Extension-List header to identify external JARs that the application requires at run time.
Działanie Ensure that the external JARs that are listed in the Extension-List header are available as bundles in the bundle repository.
CWSAL0051E: An attempt was made to update an OSGi application asset. This is not yet supported.
Objaśnienie The update of an OSGi application asset with a new binary is not yet supported.
Działanie If you need to do more than update the bundle versions within the existing asset, please uninstall the asset before importing its replacement.
Temat Skorowidzu    

Warunki używania | Zapis czynności

Ostatnia aktualizacja: Oct 21, 2010 8:24:21 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.eba.bla.nls.html

© Copyright IBM Corporation 2006, 2010. Wszelkie prawa zastrzeżone.
To centrum informacyjne jest oparte na technologii Eclipse. (http://www.eclipse.org)