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