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/ |
Action | If the new registration takes priority over the existing registration, either unregister or modify the existing registration. |
Action | Check that the id of the service reference is correct. |
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. |