Express (Distributed operating systems), v8.0 > Reference > Messages
CWSAJ
CWSAJ0001E: The name parameter has not been specified and is required.
Explanation The command requires the name parameter to be specified. Action Reissue the command specifying the name.
CWSAJ0002E: A bundle repository with the name {0} already exists.
Explanation An attempt was made to define a new bundle repository, but the specified name is already in use. Action Specify a different name.
CWSAJ0003E: The bundle repository at {0} is already defined as name {1}.
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.
CWSAJ0006E: The bundle repository {0} does not exist.
Explanation An attempt was made to modify the bundle repository, but it does not exist. Action Create the bundle repository.
CWSAJ0008E: The specified file {0} does not contain a valid bundle manifest.
Explanation The specified file is not an OSGi bundle. Action Check and correct the bundle manifest of the supplied file.
CWSAJ0009E: The bundle {1} with version {2}, defined in the file {0}, already exists in the repository.
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.
CWSAJ0010E: The specified bundle {0} with version {1} does not exist in the local bundle repository.
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.
CWSAJ0011E: An internal error occurred. The repository generator service is not available from the OSGi service registry.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAJ0012E: An internal error occurred. Cannot find the Launcher service.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAJ0013E: Unable to obtain required feature capabilities for features like the JPA2 feature.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAJ0014E: An internal error occurred. Attempted to generate an AriesApplicationModel object from a null application manifest.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAJ0015E: An internal error occurred. Attempted to generate an AriesApplicationModel object from a null deployment manifest.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAJ0016E: The name parameter has not been specified and is required.
Explanation The name parameter is required for the addExternalBundleRepository command. Action Reissue the command and specify the name of the external bundle repository.
CWSAJ0017E: The URL parameter has not been specified and is required.
Explanation The URL parameter is required for the addExternalBundleRepository command. Action Reissue the command and specify the URL of the external bundle repository.
CWSAJ0018E: It is not possible to model the Aries application {0} because some of its required components are still being downloaded.
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.
CWSAJ0019E: An internal error occurred. Attempted to generate an AriesApplicationModel object from a non-file URL {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAJ0020E: An internal error occurred extracting bundle {0} from the Composite Bundle Archive, {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAJ0021E: A problem occurred processing the manifest for the Composite Bundle Archive, {0}.
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.
CWSAJ0022E: Composite Bundle Archive, {0}, has a deployment dependency on another Composite Bundle Archive, {1}.
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.
CWSAJ0023E: The following bundles that the Composite Bundle Archive, {0}, requires cannot be found in the internal bundle repository: {1}.
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.
CWSAJ0024E: The CompositeBundle-Content header in Composite Bundle Archive {0} must contain only bundles with an exact version. The following entries are not valid: {1}.
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.
CWSAJ0025I: OSGi application console
Display commands: These commands work only if connected to a framework
ss() - This command gives the summary information about the installed bundles.
bundles() - This command gives comprehensive information about the installed bundles.
packages() - This command gives information about the imported/exported packages.
services() - This command gives information about the registered Services.
bundle( <bundleID>) - This command gives information about the specified bundle
headers( <bundleID>) - This command gives information about the headers associated with the specified bundle
packages( <bundle ID>) - This command gives information about the exported packages for this bundle.
packages( <package Name>) - This command gives information about the specified package.
services( <service ID>) - This command gives information about the specified service.
services( <OSGI Filter>) - This command gives information about the services matching the filter.
refresh() - This command refreshes the internal OSGi application console cache with the latest information about the state of the framework.
Framework commands:
list() - This command lists the available frameworks that you can connect to.
connect( <Framework id>) - This command connects to the specified framework.
connect( <Bundle Name>, <Bundle Version>, <Node Name>, <Server Name>) - This command connects to the specified framework.
Controlling Bundles:
start( <bundleID>) - This command starts the requested bundle.
stop( <bundleID> - This command stops the requested bundle.
Explanation None. Action None.
CWSAJ0026E: Unable to get bundle information because we have not connected to a framework.
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.
CWSAJ0027E: Unable to get service information because we have not connected to a framework.
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.
CWSAJ0028E: Unable to find bundle with bundle ID {0}.
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.
CWSAJ0029E: Unable to find service with service ID {0}.
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.
CWSAJ0030E: Unable to get header information because we have not connected to a framework.
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.
CWSAJ0031E: Bundle {0} is already started.
Explanation We cannot start the bundle because it is already started. Action No action is required.
CWSAJ0032I: Bundle {0} started successfully.
Explanation This message is for informational purposes only. Action No action is required.
CWSAJ0033E: Bundle {0} is already stopped.
Explanation We can not stop the bundle because it is already stopped. Action No action is required.
CWSAJ0034I: Bundle {0} stopped successfully.
Explanation This message is for informational purposes only. Action No action is required.
CWSAJ0035I: Connecting to framework {0} on node {1} and server {2}.
Explanation You are currently connecting to the framework. Action No action is required.
CWSAJ0036I: Successfully connected to framework {0}.
Explanation This message is for informational purposes only. Action No action is required.
CWSAJ0037E: Unable to connect to a framework with ID {0}.
Explanation A framework with the specified ID could not be found. Action Check that the framework ID is valid and retry the command.
CWSAJ0038E: Unable to connect to a framework with framework name {0}, node name {1} and server name {2}.
Explanation A framework with the specified attributes could not be found. Action Check that the framework attributes are valid and retry the command.
CWSAJ0039I: Valid frameworks are:
Explanation This message is for informational purposes only. Action No action is required.
CWSAJ0040I: Starting Bundle {0}.
Explanation This message is for informational purposes only. Action No action is required.
CWSAJ0041E: Bundle {0} cannot start. It is currently in {1} state.
Explanation The bundle cannot be started. Action Refer to accompanying error messages for more information about why this bundle cannot start.
CWSAJ0042I: Stopping Bundle {0}.
Explanation This message is for informational purposes only. Action No action is required.
CWSAJ0043E: Bundle {0} cannot stop. It is currently in {1} state.
Explanation The bundle cannot be stopped. Action Refer to accompanying error messages for more information about why this bundle cannot stop.
CWSAJ0044E: Unable to find package with package ID {0}.
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.
CWSAJ0045E: Unable to find package with location {0}.
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.
CWSAJ0046E: Unable to find package with package name {0}.
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.
CWSAJ0047E: Service filter is not valid: {0}.
Explanation The service filter supplied is not valid. Action Check that the service filter is valid and retry the command.
CWSAJ0048E: Unable to get package information because we have not connected to a framework.
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.
CWSAJ0049E: Cannot delete the bundle {0} because the following Composite Bundle Archives have a dependency on the bundle: {1}.
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.
CWSAJ0050E: The connection is no longer available. Please check available connections and reconnect if required.
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.
CWSAJ0051E: The asset {0} supplied is not an EBA asset.
Explanation The asset supplied is not an enterprise bundle archive (EBA) asset. Action Make sure the asset supplied is an EBA asset.
CWSAJ0052E: An internal error has occurred. Unable to find the deployment manifest from the EBA asset {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action This exception is unexpected. The cause is not immediately known.
CWSAJ0053E: Unable to find the deployment manifest from the location {0}.
Explanation The deployment manifest, DEPLOYMENT.MF, to import does not exist. Action Check that the path of the deployment manifest is correct.
CWSAJ0054E: The deployment manifest content is not correct. The following extra bundles are required {0}.
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.
CWSAJ0055E: The deployment manifest content is not correct. The following bundles are redundant: {0}.
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.
CWSAJ0056E: An internal error occurred. The resolving process does not generate a list of bundles to be installed.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAJ0057E: The deployment manifest to import cannot be resolved. The unsatisfied requirements are {0}.
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.
CWSAJ0058E: The deployment manifest to import is not valid for the asset {0} because it does not meet the requirements in the application manifest.
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.
CWSAJ0059E: The {0} parameter has not been specified and is required for the command {1}.
Explanation This command requires the specified parameter. Action Retry the command and specify the required parameter.
CWSAJ0060E: Unable to create the directory structure {0}.
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.
CWSAJ0061E: Unable to create the directory structure {0}.
Explanation The directory cannot be created. Action Check that storage space exists, and that the product has the necessary permissions to create the directory.
CWSAJ0062E: Unable to find the EBA asset {0}.
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.
CWSAJ0063E: Cannot install the Composite Bundle Archive, {0}, because the following export packages differ from those contained by the Composite Bundle Archive: {1}
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.
CWSAJ0064E: The specified file {0} is not a JAR or a Composite Bundle Archive.
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).
CWSAJ0065E: The specified file {0} cannot be parsed as a manifest file because of exception {1}
Explanation The specified file does not appear to be a valid manifest file. Action Check the supplied file is a valid manifest file.
CWSAJ0066E: The string {0} does not match the correct syntax of symbolicname;version.
Explanation The string supplied in the list of bundles to remove could not be processed because it did not match the expected syntax. Action Correct the syntax of the supplied string.
CWSAJ0067E: An internal error occurred. Metadata for the bundles {0} could not be removed from the internal bundle repository. The exception was {1}
Explanation The bundles could not be removed from the internal bundle repository. The system might now be in an inconsistent state. Action Discard the changes in the current workspace, and attempt to remove the bundles one at a time.
CWSAJ0068E: An internal error occurred. Metadata for the bundles {0} could not be removed from the internal bundle repository. Also, the bundles {1} could not be deleted from the repository. The exception was {2}
Explanation Some bundles could not be deleted from the internal bundle repository, and others could not have their metadata removed. The system might now be in an inconsistent state. Action Discard the changes in the current workspace, and attempt to remove the bundles one at a time.
CWSAJ0069E: The bundles {0} could not be removed from the internal bundle repository. All other bundles {1} have been successfully removed.
Explanation Some bundles could not be deleted from the internal bundle repository. Action Stop any applications that might be using the bundles that could not be deleted, then attempt to remove them again.
CWSAJ0070E: The bundle {0} contained in the composite bundle archive {1} does not contain a valid bundle manifest.
Explanation The specified file is not an OSGi bundle. Action Check and correct the bundle manifest of the supplied file.
CWSAJ0071E: An internal error occurred. A runtime service is not available from the OSGi service registry: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/
CWSAJ0072E: The cuName parameter has not been specified and is required.
Explanation The command requires the cuName parameter to be specified. Action Reissue the command specifying the cuName.
CWSAJ0073E: The symbolicName parameter has not been specified and is required.
Explanation The command requires the symbolicName parameter to be specified. Action Reissue the command specifying the symbolicName.
CWSAJ0074E: The version parameter has not been specified and is required.
Explanation The command requires the version parameter to be specified. Action Reissue the command specifying the version.
CWSAJ0075E: The extension with symbolic name {0} and version {1} has already been added to the composition unit.
Explanation This extension is already included in the composition unit. Action No action is required.
CWSAJ0076E: The symbolic name {0} and version {1} do not match any available extension in any available bundle repository.
Explanation There is no composite bundle with the specified symbolic name and version in any repository available to the environment. Action Either add the composite bundle to an available repository, or select a different composite bundle to add as an extension.
CWSAJ0077E: The symbolic name {0} and version {1} do not match any existing extension.
Explanation There are no extensions on the composition unit that match the specified symbolic name and version. Action No action is required.
CWSAJ0078E: A resolution problem has occurred while adding an extension to composition unit {0}. The exception is: {1}
Explanation The system cannot resolve the selected extension in conjunction with the current deployment of the asset. Bundles might have missing dependencies, be incompatible, or not exist. Action Inspect the error. Make any neccessary changes to the asset and to the extension, then reapply the extension.
CWSAJ0079E: A resolution problem has occurred while removing an extension from composition unit {0}. The exception is: {1}
Explanation The system cannot resolve the selected extension in conjunction with the current deployment of the asset. Bundles might have missing dependencies, be incompatible, or not exist. Action Inspect the error. Make any neccessary changes to the asset then remove, as a set, the extension and any other interdependent extensions.
CWSAJ0080E: The Composite Bundle Archive (CBA) {0} is not valid. Packages imported by bundles in the CBA are missing. The following problems were reported: {1}
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.
CWSAJ0081E: Cannot add extension(s) because the composition unit is deployed on the following targets, which do not support application extension: {0}
Explanation The targets which the composition unit is deployed against do not all support the application extension functionality. Action Ensure the composition unit that you wish to add extensions to is deployed on targets that support the application extension functionality.
CWSAJ0082W: The application extension functionality is not available for this composition unit because the composition unit is deployed on the following targets, which do not support application extension: {0}
Explanation The targets which the composition unit is deployed against do not all support the application extension functionality. Action Ensure the composition unit that you wish to add extensions to is deployed on targets that support the application extension functionality.
CWSAJ0083W: The Composite Bundle Archive (CBA) {0} exports services that are not provided by bundles contained in the CBA. These services will not be available for use by bundles outside the CBA. The following problems were reported: {1}
Explanation A CBA cannot export services for which there is no Blueprint declaration or Bundle-ExportService: header on one of bundles in the CBA. Action Either add the missing Blueprint service declarations to the CBA contents, or remove the details of the unsatisfied exports from the composite manifest, COMPOSITEBUNDLE.MF.
CWSAJ0084W: 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}
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.