Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/, or on the WebSphere Application Server for z/OS Support page at http://www.ibm.com/software/webservers/appserv/zos_os390/support/. |
Explanation | The full set of dependencies for an enterprise bundle archive (EBA) cannot be resolved. |
Action | See the accompanying messages for information about the dependencies that cannot be provisioned. Correct the problems, reinstall the EBA, and try again. |
Explanation | Cannot attach a fragment that has an extension directive set. Applications must not set this directive. The extension directive applies only when the Fragment-Host is the System Bundle. |
Action | Remove the extension directive from the application. |
Explanation | An bundle repository could not be added to the resolver. The most common cause is that the repository URL is not valid. |
Action | Check that the bundle repository URL is valid and that the bundle repository is well-formed. |
Explanation | The runtime environment attempted to identify some application or use-bundle content, but could not find it in any bundle repository. The most common cause is that the content has been removed from the repository. This might mean that the application is unable to resolve in the future. |
Action | Add the missing bundle to a configured bundle repository. |