Explanation | During installation of the application, the bundle could not be located. |
Action | Request that the bundle is downloaded by using either the BundleCacheManager MBean or the administrative console. |
Explanation | An exception occurred when trying to install the bundle into the OSGi framework. |
Action | Investigate the cause of the underlying exception. |
Explanation | An exception occurred when trying to start the bundle. |
Action | Refer to the standard error output log for the complete stack trace and resolve the exception. |
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 | 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 | There was an attempt to register a service that is already registered. The new registration was ignored. |
Action | If the new registration takes priority over the existing registration, either unregister or modify the existing registration. |
Explanation | There was an attempt to unregister a service, but no service with that id is registered. |
Action | Check that the id of the service reference is correct. |
Explanation | There was an attempt to modify a service, but no service with that id is registered. |
Action | Check that the id of the service reference is correct. |
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 format of the permissions file is not correct. |
Action | Check that the content of the permissions file is correct and properly formatted. |
Explanation | An attempt to access and read in the contents of the permissions file failed. |
Action | See the information in the exception. Check that the the permissions file exists and can be accessed. |
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 | There was a problem when registering the JMX MBeans. You cannot use the OSGi application console commands to view this application. Installation of the application is not affected. |
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 | There was a problem when unregistering the JMX MBeans. Uninstallation of the application is not affected. |
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 MBeanServer cannot be found in the OSGi service registry. You cannot use the OSGi application console commands to view this application. Installation of the application is not affected. |
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 | There was a stop request for an application that is already stopped. A previous failed stop request might be the cause. The server log contains details of any previous failure. |
Action | Restart the application server. |
Explanation | There was an update request for an application that is stopped. A previous failed stop request might be the cause. The server log contains details of any previous failure. |
Action | Restart the application server. |
Explanation | There was a problem when attempting to clear up unused shared bundles. |
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 | There was a problem when attempting to clear up unused shared bundles. |
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 | There was a problem when attempting to clear up unused shared bundles. |
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 | There was a problem when attempting to clear up unused shared bundles. |
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 | There was a problem when attempting to clear up unused shared bundles. |
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 | There was a problem when attempting to clear up unused shared bundles. |
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 | There was a problem when attempting to clear up unused shared bundles. |
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 | To save system resources, the application server removes any shared OSGi bundles that are no longer used by any applications. To work out which bundles are being used, the runtime environment analyzes their service dependencies. If these cannot be determined, some shared bundles might be removed even though they are providing services that are in use. If these bundles are removed then some shared bundles might no longer function correctly. |
Action | Check the blueprint metadata for the named bundle and change the invalid filter so that it uses the correct syntax. |
Explanation | To save system resources, the application server removes any shared OSGi bundles that are no longer used by any applications. To work out which bundles are being used, the runtime environment analyzes their service dependencies. If these cannot be determined, some shared bundles might be removed even though they are providing services that are in use. If these bundles are removed then some shared bundles might no longer function correctly. |
Action | Check the blueprint metadata for the named bundle and change the invalid filter so that it uses the correct syntax. |
Explanation | To save system resources, the application server removes any shared OSGi bundles that are no longer used by any applications. To work out which bundles are being used, the runtime environment analyzes their service dependencies. If these cannot be determined, some shared bundles might be removed even though they are providing services that are in use. If these bundles are removed then some shared bundles might no longer function correctly. |
Action | Check the blueprint metadata for the named bundle and change the invalid filter so that it uses the correct syntax. |
Explanation | To save system resources, the application server removes any shared OSGi bundles that are no longer used by any applications. To work out which bundles are being used, the runtime environment analyzes their service dependencies. If these cannot be determined, some shared bundles might be removed even though they are providing services that are in use. If these bundles are removed then some shared bundles might no longer function correctly. |
Action | Check the blueprint metadata for the named bundle and change the invalid filter so that it uses the correct syntax. |
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 | 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 | There were exceptions installing at least one of the new bundles. These exceptions can be caused by bundle errors or system errors. |
Action | Inspect previous errors and exceptions in the log, to see why the bundle install failed. Fix any problems with the new bundles. |
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 Aries OSGi runtime services could not be found in the service registry. |
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 | Certain updates to the application cannot be applied in place. In particular, new provisioned packages or services might require a full restart of the application. |
Action | To determine which changes require the new packages or services, inspect the bundle manifests of any updated bundles for new imported packages or packages that are imported with a different version range. Also, check any blueprint descriptors for new service references. |
Explanation | As part of an in-place update, the system has to restart any bundles that have a direct or indirect package dependency, or a Require-Bundle dependency, on any of the updated bundles. |
Action | To determine why a bundle needs to be restarted, inspect its bundle manifest. Look for any package imported or Require-Bundle header that uses one of the updated bundles, or that uses any other bundle that is part of the set of bundles to be restarted. |
Explanation | It was not possible to start an Aries application. One or more bundles may have failed to resolve or start. |
Action | Inspect the logs for errors relating to this problem. Fix any problems in the application associated with these errors. |
Explanation | There was a problem stopping an Aries application. |
Action | Inspect the logs for errors relating to this problem. Fix any problems in the application associated with these errors. |
Explanation | It was not possible to update an Aries application. The update was rolled back. |
Action | Inspect the logs for errors relating to this problem. Fix any problems in the application associated with these errors. |
Explanation | It was not possible to update an Aries application. The update could not be rolled back. |
Action | Inspect the logs for errors relating to this problem. Fix any problems in the application associated with these errors. |