EBAADMIN0073E=CWSAJ0073E: The symbolicName parameter has not been specified and is required. The command requires the symbolicName parameter to be specified. Reissue the command specifying the symbolicName. EBAADMIN0053E=CWSAJ0053E: Unable to find the deployment manifest from the location {0}. The deployment manifest, DEPLOYMENT.MF, to import does not exist. Check that the path of the deployment manifest is correct. EBAADMIN0069E=CWSAJ0069E: The bundles {0} could not be removed from the internal bundle repository. All other bundles {1} have been successfully removed. Some bundles could not be deleted from the internal bundle repository. Stop any applications that might be using the bundles that could not be deleted, then attempt to remove them again. EBAADMIN0033E=CWSAJ0033E: Bundle {0} is already stopped. You can not stop the bundle because it is already stopped. No action is required. EBAADMIN0049E=CWSAJ0049E: Cannot delete the bundle {0} because the following Composite Bundle Archives have a dependency on the bundle: {1}. A bundle cannot be deleted from the internal bundle repository if a Composite Bundle Archive depends on that bundle. To delete the bundle, first delete the Composite Bundle Archives listed, then delete the bundle. EBAADMIN0013E=CWSAJ0013E: Unable to obtain required feature capabilities for features like the JPA2 feature. CMSG0001 CMSG0002 EBAADMIN0029E=CWSAJ0029E: Unable to find service with service ID {0}. The service ID that was supplied to the command does not match a service in the registry. Retry the command with a valid service ID. EBAADMIN0009E=CWSAJ0009E: The bundle {1} with version {2}, defined in the file {0}, already exists in the repository. The bundle cannot be added to the repository because the bundle already exists in the repository. 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. EBAADMIN0072E=CWSAJ0072E: The cuName parameter has not been specified and is required. The command requires the cuName parameter to be specified. Reissue the command specifying the cuName. CBA_WITH_MISSING_SERVICE_IMPORTS=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} 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. EBAADMIN0052E=CWSAJ0052E: An internal error has occurred. Unable to find the deployment manifest from the EBA asset {0}. CMSG0001 CMSG0001 EBAADMIN0068E=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} 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. Discard the changes in the current workspace, and attempt to remove the bundles one at a time. EBAADMIN0032I=CWSAJ0032I: Bundle {0} started successfully. This message is for informational purposes only. No action is required. EBAADMIN0048E=CWSAJ0048E: Unable to get package information because you have not connected to a framework. You are not currently connected to a framework. Use the connect command to connect to a framework. For a list of available frameworks, use the list() command. EBAADMIN0012E=CWSAJ0012E: An internal error occurred. Cannot find the Launcher service. CMSG0001 CMSG0002 EBAADMIN0028E=CWSAJ0028E: Unable to find bundle with bundle ID {0}. The bundle ID that was supplied to the command does not match a bundle in the framework. Retry the command with a valid bundle ID. EBAADMIN0008E=CWSAJ0008E: The specified file {0} does not contain a valid bundle manifest. The specified file is not an OSGi bundle. Check and correct the bundle manifest of the supplied file. EBAADMIN0071E=CWSAJ0071E: An internal error occurred. A runtime service is not available from the OSGi service registry: {0} CMSG0001 CMSG0002 EBAADMIN0051E=CWSAJ0051E: The asset {0} supplied is not an EBA asset. The asset supplied is not an enterprise bundle archive (EBA) asset. Make sure the asset supplied is an EBA asset. EBAADMIN0067E=CWSAJ0067E: An internal error occurred. Metadata for the bundles {0} could not be removed from the internal bundle repository. The exception was {1} The bundles could not be removed from the internal bundle repository. The system might now be in an inconsistent state. Discard the changes in the current workspace, and attempt to remove the bundles one at a time. EBAADMIN0031E=CWSAJ0031E: Bundle {0} is already started. You cannot start the bundle because it is already started. No action is required. EBAADMIN0047E=CWSAJ0047E: Service filter is not valid: {0}. The service filter supplied is not valid. Check that the service filter is valid and retry the command. EBAADMIN0011E=CWSAJ0011E: An internal error occurred. The repository generator service is not available from the OSGi service registry. CMSG0001 CMSG0002 EBAADMIN0027E=CWSAJ0027E: Unable to get service information because you have not connected to a framework. You are not currently connected to a framework. Use the connect command to connect to a framework. For a list of available frameworks, use the list() command. EBAADMIN0070E=CWSAJ0070E: The bundle {0} contained in the composite bundle archive {1} does not contain a valid bundle manifest. The specified file is not an OSGi bundle. Check and correct the bundle manifest of the supplied file. CBA_WITH_MISSING_PACKAGE_IMPORTS=CWSAJ0080E: 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. EBAADMIN0050E=CWSAJ0050E: The connection is no longer available. Please check available connections and reconnect if required. The framework that you were connected to is no longer available. This might be because an application has stopped. Check whether the framework is still available and reconnect if required. EBAADMIN0066E=CWSAJ0066E: The string {0} does not match the correct syntax of symbolicname;version. The string supplied in the list of bundles to remove could not be processed because it did not match the expected syntax. Correct the syntax of the supplied string. EBAADMIN0030E=CWSAJ0030E: Unable to get header information because you have not connected to a framework. You are not currently connected to a framework. Use the connect command to connect to a framework. For a list of available frameworks, use the list() command. EBAADMIN0046E=CWSAJ0046E: Unable to find package with package name {0}. The package name that was supplied to the command did not match a package in the framework. Check that the package name is valid and retry the command. EBAADMIN0010E=CWSAJ0010E: The specified bundle {0} with version {1} does not exist in the local bundle repository. The bundle cannot be shown or deleted because no bundle with that name exists. Check and correct the version or symbolic name of the bundle. EBAADMIN0026E=CWSAJ0026E: Unable to get bundle information because you have not connected to a framework. You are not currently connected to a framework. Use the connect command to connect to a framework. For a list of available frameworks, use the list() command. EBAADMIN0006E=CWSAJ0006E: The bundle repository {0} does not exist. An attempt was made to modify the bundle repository, but it does not exist. Create the bundle repository. EBAADMIN0065E=CWSAJ0065E: The specified file {0} cannot be parsed as a manifest file because of exception {1} The specified file does not appear to be a valid manifest file. Check the supplied file is a valid manifest file. EBAADMIN0045E=CWSAJ0045E: Unable to find package with location {0}. The package location that was supplied to the command did not match a package location in the framework. Check that the package location is valid and retry the command. EBAADMIN0025I=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. None. None. EBAADMIN0064E=CWSAJ0064E: The specified file {0} is not a JAR or a Composite Bundle Archive. The name of the specified file does not end with either a .jar or a .cba file extension. Check and correct the name of the supplied file. The supplied file must be a valid JAR or Composite Bundle Archive (CBA). EBAADMIN0044E=CWSAJ0044E: Unable to find package with package ID {0}. The package ID that was supplied to the command did not match a package in the framework. Check that the package ID is valid and retry the command. EBAADMIN0024E=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}. A CompositeBundle-Content entry must use a format similar to 'bundle.name;version="[1.0.0,1.0.0]"'. Ensure that entries in the CompositeBundle-Content header in the composite bundle manifest file specify an exact version and use the correct format. EBAADMIN0063E=CWSAJ0063E: Cannot install the Composite Bundle Archive, {0}, because the following export packages differ from those contained by the Composite Bundle Archive: {1} A Composite Bundle Archive (CBA) can export only packages that the bundles it contains also export. The attributes and directives must also match. Correct the composite manifest, COMPOSITEBUNDLE.MF, so that it exports packages that the bundles that the CBA contains also export. EBAADMIN0082W=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} The targets which the composition unit is deployed against do not all support the application extension functionality. Ensure the composition unit that you wish to add extensions to is deployed on targets that support the application extension functionality. EBAADMIN0043E=CWSAJ0043E: Bundle {0} cannot stop. It is currently in {1} state. The bundle cannot be stopped. Refer to accompanying error messages for more information about why this bundle cannot stop. EBAADMIN0059E=CWSAJ0059E: The {0} parameter has not been specified and is required for the command {1}. This command requires the specified parameter. Retry the command and specify the required parameter. EBAADMIN0039I=CWSAJ0039I: Valid frameworks are: This message is for informational purposes only. No action is required. EBAADMIN0023E=CWSAJ0023E: The following bundles that the Composite Bundle Archive, {0}, requires cannot be found in the internal bundle repository: {1}. A Composite Bundle Archive can be deployed only if all the dependencies can be found in the internal bundle repository. Ensure that the Composite Bundle Archive dependencies listed are either in the Composite Bundle Archive or installed in the internal bundle repository. ADD_RESOLVE_FAILED=CWSAJ0078E: A resolution problem has occurred while adding an extension to composition unit {0}. The exception is: {1} 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. Inspect the error. Make any neccessary changes to the asset and to the extension, then reapply the extension. EBAADMIN0003E=CWSAJ0003E: The bundle repository at {0} is already defined as name {1}. An attempt was made to define a new bundle repository, but another bundle repository already uses the specified URL. Specify a different URL. EBAADMIN0019E=CWSAJ0019E: An internal error occurred. Attempted to generate an AriesApplicationModel object from a non-file URL {0}. CMSG0001 CMSG0002 EBAADMIN0062E=CWSAJ0062E: Unable to find the EBA asset {0}. You imported a deployment manifest to an asset, but the enterprise bundle archive (EBA) asset does not exist. Check that the EBA asset is installed. EBAADMIN0042I=CWSAJ0042I: Stopping Bundle {0}. This message is for informational purposes only. No action is required. REMOVE_RESOLVE_FAILED=CWSAJ0079E: A resolution problem has occurred while removing an extension from composition unit {0}. The exception is: {1} 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. Inspect the error. Make any neccessary changes to the asset then remove, as a set, the extension and any other interdependent extensions. EBAADMIN0058E=CWSAJ0058E: 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. EBAADMIN0022E=CWSAJ0022E: Composite Bundle Archive, {0}, has a deployment dependency on another Composite Bundle Archive, {1}. Nesting of Composite Bundle Archives is not supported. Check that the Composite Bundle Archive depends only on bundles in the CompositeBundle-Content header of the Composite Bundle Archive manifest. EBAADMIN0038E=CWSAJ0038E: Unable to connect to a framework with framework name {0}, node name {1} and server name {2}. A framework with the specified attributes could not be found. Check that the framework attributes are valid and retry the command. EBAADMIN0002E=CWSAJ0002E: A bundle repository with the name {0} already exists. An attempt was made to define a new bundle repository, but the specified name is already in use. Specify a different name. EBAADMIN0018E=CWSAJ0018E: It is not possible to model the Aries application {0} because some of its required components are still being downloaded. One or more bundles that the application requires are being downloaded. The application cannot be modeled until all downloads are complete. Wait until all the required bundles are downloaded, then try again. EBAADMIN0081E=CWSAJ0081E: Cannot add extension(s) because the composition unit is deployed on the following targets, which do not support application extension: {0} The targets which the composition unit is deployed against do not all support the application extension functionality. Ensure the composition unit that you wish to add extensions to is deployed on targets that support the application extension functionality. EBAADMIN0061E=CWSAJ0061E: Unable to create the directory structure {0}. The directory cannot be created. Check that storage space exists, and that the product has the necessary permissions to create the directory. EBAADMIN0077E=CWSAJ0077E: The symbolic name {0} and version {1} do not match any existing extension. There are no extensions on the composition unit that match the specified symbolic name and version. No action is required. EBAADMIN0041E=CWSAJ0041E: Bundle {0} cannot start. It is currently in {1} state. The bundle cannot be started. Refer to accompanying error messages for more information about why this bundle cannot start. EBAADMIN0057E=CWSAJ0057E: The deployment manifest to import cannot be resolved. The unsatisfied requirements are {0}. The deployment manifest, DEPLOYMENT.MF, to import has a requirement that cannot be satisfied. Check that the new deployment manifest is complete and includes the bundles needed to resolve the enterprise bundle archive (EBA) asset. EBAADMIN0021E=CWSAJ0021E: A problem occurred processing the manifest for the Composite Bundle Archive, {0}. Either the manifest is not present, or the name or format are not correct. Check that the manifest is present and formatted and named correctly. EBAADMIN0037E=CWSAJ0037E: Unable to connect to a framework with ID {0}. A framework with the specified ID could not be found. Check that the framework ID is valid and retry the command. CBA_WITH_EXTRA_SERVICE_EXPORTS=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} A CBA cannot export services for which there is no Blueprint declaration or Bundle-ExportService: header on one of bundles in the CBA. 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. EBAADMIN0001E=CWSAJ0001E: The name parameter has not been specified and is required. The command requires the name parameter to be specified. Reissue the command specifying the name. EBAADMIN0017E=CWSAJ0017E: The URL parameter has not been specified and is required. The URL parameter is required for the addExternalBundleRepository command. Reissue the command and specify the URL of the external bundle repository. EBAADMIN0060E=CWSAJ0060E: Unable to create the directory structure {0}. You attempted to export a deployment manifest to a directory that does not exist, and the directory structure cannot be created. Check that storage space exists, and that the product has the necessary permissions to create the directory. EBAADMIN0076E=CWSAJ0076E: The symbolic name {0} and version {1} do not match any available extension in any available bundle repository. There is no composite bundle with the specified symbolic name and version in any repository available to the environment. Either add the composite bundle to an available repository, or select a different composite bundle to add as an extension. EBAADMIN0040I=CWSAJ0040I: Starting Bundle {0}. This message is for informational purposes only. No action is required. EBAADMIN0056E=CWSAJ0056E: An internal error occurred. The resolving process does not generate a list of bundles to be installed. CMSG0001 CMSG0002 EBAADMIN0036I=CWSAJ0036I: Successfully connected to framework {0}. This message is for informational purposes only. No action is required. EBAADMIN0020E=CWSAJ0020E: An internal error occurred extracting bundle {0} from the Composite Bundle Archive, {1}. CMSG0001 CMSG0002 EBAADMIN0016E=CWSAJ0016E: The name parameter has not been specified and is required. The name parameter is required for the addExternalBundleRepository command. Reissue the command and specify the name of the external bundle repository. EBAADMIN0075E=CWSAJ0075E: The extension with symbolic name {0} and version {1} has already been added to the composition unit. This extension is already included in the composition unit. No action is required. EBAADMIN0055E=CWSAJ0055E: The deployment manifest content is not correct. The following bundles are redundant: {0}. The deployment manifest, DEPLOYMENT.MF, to import includes bundles that are not needed to resolve the enterprise bundle archive (EBA) asset. Check that the new deployment manifest does not include the bundles that are listed in the message. EBAADMIN0035I=CWSAJ0035I: Connecting to framework {0} on node {1} and server {2}. You are currently connecting to the framework. No action is required. EBAADMIN0015E=CWSAJ0015E: An internal error occurred. Attempted to generate an AriesApplicationModel object from a null deployment manifest. CMSG0001 CMSG0002 EBAADMIN0074E=CWSAJ0074E: The version parameter has not been specified and is required. The command requires the version parameter to be specified. Reissue the command specifying the version. EBAADMIN0054E=CWSAJ0054E: The deployment manifest content is not correct. The following extra bundles are required {0}. The deployment manifest, DEPLOYMENT.MF, to import does not include all the bundles needed to resolve the enterprise bundle archive (EBA) asset. Check that the new deployment manifest includes all the bundles that are listed in the message. EBAADMIN0034I=CWSAJ0034I: Bundle {0} stopped successfully. This message is for informational purposes only. No action is required. EBAADMIN0014E=CWSAJ0014E: An internal error occurred. Attempted to generate an AriesApplicationModel object from a null application manifest. CMSG0001 CMSG0002