[AIX HP-UX Linux Solaris Windows][z/OS]

CWSAJ

Explanation The command requires the name parameter to be specified.
Action Reissue the command specifying the name.
Explanation An attempt was made to define a new bundle repository, but the specified name is already in use.
Action Specify a different name.
Explanation An attempt was made to define a new bundle repository, but another bundle repository already uses the specified URL.
Action Specify a different URL.
Explanation An attempt was made to modify the bundle repository, but it does not exist.
Action Create the bundle repository.
Explanation The specified file is not an OSGi bundle.
Action Check and correct the bundle manifest of the supplied file.
Explanation The bundle cannot be added to the repository because the bundle already exists in the repository.
Action Check whether the bundle in the repository is the correct one. If the bundle in the repository is not correct, remove that bundle from the repository before you add the correct bundle.
Explanation The bundle cannot be shown or deleted because no bundle with that name exists.
Action Check and correct the version or symbolic name of the bundle.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/
Explanation The name parameter is required for the addExternalBundleRepository command.
Action Reissue the command and specify the name of the external bundle repository.
Explanation The URL parameter is required for the addExternalBundleRepository command.
Action Reissue the command and specify the URL of the external bundle repository.
Explanation One or more bundles that the application requires are being downloaded. The application cannot be modeled until all downloads are complete.
Action Wait until all the required bundles are downloaded, then try again.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/
Explanation Either the manifest is not present, or the name or format are not correct.
Action Check that the manifest is present and formatted and named correctly.
Explanation Nesting of Composite Bundle Archives is not supported.
Action Check that the Composite Bundle Archive depends only on bundles in the CompositeBundle-Content header of the Composite Bundle Archive manifest.
Explanation A Composite Bundle Archive can be deployed only if all the dependencies can be found in the internal bundle repository.
Action Ensure that the Composite Bundle Archive dependencies listed are either in the Composite Bundle Archive or installed in the internal bundle repository.
Explanation A CompositeBundle-Content entry must use a format similar to 'bundle.name;version="[1.0.0,1.0.0]"'.
Action Ensure that entries in the CompositeBundle-Content header in the composite bundle manifest file specify an exact version and use the correct format.
Explanation None.
Action None.
Explanation You are not currently connected to a framework.
Action Use the connect command to connect to a framework. For a list of available frameworks, use the list() command.
Explanation You are not currently connected to a framework.
Action Use the connect command to connect to a framework. For a list of available frameworks, use the list() command.
Explanation The bundle ID that was supplied to the command does not match a bundle in the framework.
Action Retry the command with a valid bundle ID.
Explanation The service ID that was supplied to the command does not match a service in the registry.
Action Retry the command with a valid service ID.
Explanation You are not currently connected to a framework.
Action Use the connect command to connect to a framework. For a list of available frameworks, use the list() command.
Explanation You cannot start the bundle because it is already started.
Action No action is required.
Explanation This message is for informational purposes only.
Action No action is required.
Explanation You can not stop the bundle because it is already stopped.
Action No action is required.
Explanation This message is for informational purposes only.
Action No action is required.
Explanation You are currently connecting to the framework.
Action No action is required.
Explanation This message is for informational purposes only.
Action No action is required.
Explanation A framework with the specified ID could not be found.
Action Check that the framework ID is valid and retry the command.
Explanation A framework with the specified attributes could not be found.
Action Check that the framework attributes are valid and retry the command.
Explanation This message is for informational purposes only.
Action No action is required.
Explanation This message is for informational purposes only.
Action No action is required.
Explanation The bundle cannot be started.
Action Refer to accompanying error messages for more information about why this bundle cannot start.
Explanation This message is for informational purposes only.
Action No action is required.
Explanation The bundle cannot be stopped.
Action Refer to accompanying error messages for more information about why this bundle cannot stop.
Explanation The package ID that was supplied to the command did not match a package in the framework.
Action Check that the package ID is valid and retry the command.
Explanation The package location that was supplied to the command did not match a package location in the framework.
Action Check that the package location is valid and retry the command.
Explanation The package name that was supplied to the command did not match a package in the framework.
Action Check that the package name is valid and retry the command.
Explanation The service filter supplied is not valid.
Action Check that the service filter is valid and retry the command.
Explanation You are not currently connected to a framework.
Action Use the connect command to connect to a framework. For a list of available frameworks, use the list() command.
Explanation A bundle cannot be deleted from the internal bundle repository if a Composite Bundle Archive depends on that bundle.
Action To delete the bundle, first delete the Composite Bundle Archives listed, then delete the bundle.
Explanation The framework that you were connected to is no longer available. This might be because an application has stopped.
Action Check whether the framework is still available and reconnect if required.
Explanation The asset supplied is not an enterprise bundle archive (EBA) asset.
Action Make sure the asset supplied is an EBA asset.
Explanation This exception is unexpected. The cause is not immediately known.
Action This exception is unexpected. The cause is not immediately known.
Explanation The deployment manifest, DEPLOYMENT.MF, to import does not exist.
Action Check that the path of the deployment manifest is correct.
Explanation The deployment manifest, DEPLOYMENT.MF, to import does not include all the bundles needed to resolve the enterprise bundle archive (EBA) asset.
Action Check that the new deployment manifest includes all the bundles that are listed in the message.
Explanation The deployment manifest, DEPLOYMENT.MF, to import includes bundles that are not needed to resolve the enterprise bundle archive (EBA) asset.
Action Check that the new deployment manifest does not include the bundles that are listed in the message.
Explanation This exception is unexpected. The cause is not immediately known.
Action 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/
Explanation The deployment manifest, DEPLOYMENT.MF, to import has a requirement that cannot be satisfied.
Action Check that the new deployment manifest is complete and includes the bundles needed to resolve the enterprise bundle archive (EBA) asset.
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.
Explanation This command requires the specified parameter.
Action Retry the command and specify the required parameter.
Explanation You attempted to export a deployment manifest to a directory that does not exist, and the directory structure cannot be created.
Action Check that storage space exists, and that the product has the necessary permissions to create the directory.
Explanation The directory cannot be created.
Action Check that storage space exists, and that the product has the necessary permissions to create the directory.
Explanation You imported a deployment manifest to an asset, but the enterprise bundle archive (EBA) asset does not exist.
Action Check that the EBA asset is installed.
Explanation A Composite Bundle Archive (CBA) can export only packages that the bundles it contains also export. The attributes and directives must also match.
Action Correct the composite manifest, COMPOSITEBUNDLE.MF, so that it exports packages that the bundles that the CBA contains also export.
Explanation The name of the specified file does not end with either a .jar or a .cba file extension.
Action Check and correct the name of the supplied file. The supplied file must be a valid JAR or Composite Bundle Archive (CBA).
Reference topic    

Terms and conditions for information centers | Feedback

Last updated: Sep 20, 2012 7:41:11 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.eba.admin.messages.html

© Copyright IBM Corporation 2006, 2011. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)