Explanation | The feature manager could not find a definition for the specified feature. |
Action | Check that the name of the specified feature is spelled correctly, and that the feature definition exists and is readable in the lib/features directory. |
Explanation | The feature manager could not find a bundle required by an enabled feature. |
Action | Ensure that bundles in the lib directory are readable, and that the install image is complete. |
Explanation | The feature manager could not install or uninstall the specified bundle. |
Action | See the referenced exception and generated FFDC messages for each failure. |
Explanation | An unexpected exception occurred while adding or removing one or more features from the runtime. |
Action | See the referenced exception and generated FFDC message for more information. |
Explanation | An exception occurred while changing the state of a bundle managed by the feature manager. |
Action | See the referenced exception and associated FFDC records for details. |
Explanation | The bundle cache file could not be created or read. See the referenced exception for more information. |
Action | Make sure the server directory and workarea subdirectory are writable. |
Explanation | The feature manager has begun processing enabled features. The interval (in seconds) is relative to when the platform was launched. |
Action | No action is required. |
Explanation | The feature manager has finished processing enabled features. The interval (in seconds) is relative to when the platform was launched. |
Action | No action is required. |
Explanation | No features were configured to be installed. |
Action | Update the configuration to add any required features. |
Explanation | A feature definition element matched more than one bundle. This could be because the filter is too general, or because there are old bundles in the image that match the filter. |
Action | Make sure that the filter is sufficiently specific, and that a clean install image is being used. |
Explanation | The server has started successfully. |
Action | No action is required. |
Explanation | The server has installed a set of features. |
Action | No action is required. |
Explanation | The server has removed a set of features. |
Action | No action is required. |
Explanation | The server has some test fixes from IBM installed. |
Action | A production server should not have test fixes installed. If this is a production server remove the test fixes and restart the server. |
Explanation | The server has some interim fixes installed. |
Action | No action is required. |
Explanation | The IBM-Provision-Capability header contains one or more OSGi filters with invalid syntax. |
Action | Amend the filter syntax in the IBM-Provision-Capability header. |
Explanation | The feature manager could not find the specified product install path. |
Action | Verify that a valid product path is defined for the property com.ibm.websphere.productInstall in the product properties file. |
Explanation | The feature manager found a product properties file that does not contain the property com.ibm.websphere.productInstall. |
Action | Add com.ibm.websphere.productInstall to the product properties file in etc/extensions. |
Explanation | The specified exception occurred when the feature manager attempted to read properties from the product properties file. |
Action | See the referenced exception and associated FFDC records for details. |
Explanation | The Symbolic-Name header in a feature has the attribute of superseded-by configured but its superseded attribute is set to false. |
Action | Make sure that the Symbolic-Name header has superseded and superseded-by attributes correctly configured. |
Explanation | Only public features can be specified in server.xml. |
Action | Change the server configuration to specify a public feature that provides the required function. If you are developing a feature that users should specify in their server configuration, change the feature to have public visibility by adding visibility=public as an attribute to the Subsystem-SymbolicName for the feature. |
Explanation | The server only supports features whose IBM-Feature-Version is set to 2. A number higher than 2 indicates the feature is intended for a later version of the product. |
Action | Contact the author of the feature to obtain a copy that is designed for this version of the product. |
Explanation | An exception occurred when the feature jar file was read during a packaging query. |
Action | See the referenced exception and associated FFDC records for details. |
Explanation | The feature manager could not find the specified feature content. |
Action | Check that the product has been installed correctly. If the problem persists, contact your service representative. |
Explanation | The feature manager could not understand the specified feature content. |
Action | Check that the product has been installed correctly. If the problem persists, contact your service representative. |
Explanation | The server is preparing information for a pending server package operation. |
Action | No action is required. |
Explanation | A product extension install path can not contain symbolic locations. |
Action | Update the com.ibm.websphere.productInstall property in the specified product extension properties file so that it does not contain any symbolic locations. |
Explanation | A product extension install path can not be the same as wlp.install.dir. |
Action | Update the com.ibm.websphere.productInstall property in the specified product extension properties file so that it is not the same as wlp.install.dir. |
Explanation | A BundleException was thrown by the OSGi Framework. |
Action | See the exception message for information. |
Explanation | An invalid value was specified for start-phase. |
Action | Specify a valid value for the start-phase. |
Explanation | The feature being installed already exists. |
Action | No action is required. |
Explanation | The wrong number of arguments were used to invoke the action. |
Action | Rerun the command with the correct arguments. |
Explanation | An attempt was made to run a command using invalid arguments. |
Action | Rerun the command without the invalid arguments. |
Explanation | The product extension into which the feature is to be installed is not registered. |
Action | Install the feature into a product extension that is registered, or register the missing product extension. |
Explanation | The product extension cannot be found because the registration file does not contain a location. |
Action | Correct the product extension registration so that it contains the location of the extension. |
Explanation | An unexpected error occurred when trying to read the properties file for the product extension provided in the error message. |
Action | Review the exception message for an explanation of why the file could not be read and try again. |
Explanation | The product extension directory does not exist so the feature cannot be installed into it. |
Action | Ensure the directory exists and try to install the feature again. |
Explanation | An error occurred while downloading the Subsystem archive. This could be because the URL is not valid, or a temporary network issue. The second sentence of the error message might give more detailed information on the cause of the error. |
Action | Check that the URL to the Subsystem archive is correct and try again. |
Explanation | The feature install operation downloads the Subsystem archive to a temporary file, but a temporary file could not be created. This is probably caused by a machine constraint. The second sentence of the error message might give more detailed information on the cause of the error. |
Action | It is possible that the temporary file system is full. If so, clearing space will solve this problem. |
Explanation | The Subsystem archive file provided to the install operation does not exist. |
Action | Ensure the Subsystem archive file name was provided correctly and run the install operation again. |
Explanation | The provided file name identified a directory rather than a Subsystem archive. |
Action | Ensure the Subsystem archive file name was provided correctly and run the install operation again. |
Explanation | The feature being installed depends on other features that have not yet been installed. The feature cannot be used until the feature named in the error message is installed. |
Action | Install the missing feature and run the installation again. |
Explanation | When processing the Subsystem content, a file was referenced but was not found in the archive. |
Action | Contact the Subsystem author to obtain an updated archive that contains the required content. |
Explanation | When processing the Subsystem content, some required bundles were not found in the Subsystem archive. |
Action | Contact the Subsystem author to obtain an updated archive that contains the required content. |
Explanation | It was not possible to read the Subsystem archive. |
Action | Check that the Subsystem archive is a valid, complete archive. If it is not valid, obtain a fresh archive from the provider. |
Explanation | The installation of the Subsystem archive failed because a file from the archive already exists in the installation. |
Action | Review the files that already exist. If the install operation can proceed, run the operation again using either the --when-file-exists=replace option to replace the existing files, or the --when-file-exists=ignore option to continue without the existing file. |
Explanation | Directories required by the feature being installed could not be created. |
Action | Ensure the provided directory exists and that necessary permissions are in place to allow the creation of the directory structure. Run the install operation again. |
Explanation | The feature was installed. |
Action | No action is required. |
Explanation | The --when-file-exists option must be one of fail, replace, ignore. |
Action | Provide one of the valid values of fail, replace or ignore. |
Explanation | The feature manifest files associated with the specified product extension were not found. |
Action | Verify that the directory where the feature manifests are located is valid. |
Explanation | The product extension cannot be found at the mentioned location. |
Action | Verify that the product installation location is correctly defined in the properties file for the product installation. |
Explanation | The product extension with the specified name does not exist. |
Action | Verify that the specified product extension name is valid. |
Explanation | The subsystem archive does not contain the file OSGI-INF/SUBSYSTEM.MF, which contains metadata about the subsystem. |
Action | Add the file OSGI-INF/SUBSYSTEM.MF to the archive. |
Explanation | You must use only one OSGI-INF/SUBSYSTEM.MF file to define a feature, but the archive contains two OSGI-INF/SUBSYSTEM.MF files that are specified with different case. |
Action | Delete one of the SUBSYSTEM.MF files. |