Explanation | An internal error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal error occurred when attempting to register Endpoint Manager MBean with MBean server. MBean will not be retrievable through MBean server, but this will not affect the functionality of the application. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal error occurred when attempting to unregister the Endpoint Manager MBean from the MBean server. The MBean is not retrievable through the MBean server, but this does not affect the functionality of the application. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | Notifications failed to broadcast to all registered listeners of the Endpoint Manager MBean. Notifications are sent whenever an endpoint that belongs to the Endpoint Manager changes state. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | The key that was passed in was not valid. Therefore, the key does not have a corresponding endpoint. The keys are the service's partial URL pattern, the JMS target service, or the corresponding wsdl:service and wsdl:port values. |
Action | Ensure the key is valid and contains valid service and port names within the module. |
Explanation | The value for the wsdl:service name was not recognized and its corresponding endpoints could not be found. |
Action | Ensure that the wsdl:service name that is registered with the service's WSDL file is valid. |
Explanation | The endpoint being started is already in the start state. |
Action | There is no need to start an already started endpoint. |
Explanation | The endpoint being stopped is already in the stop state. |
Action | There is no need to stop an already stopped endpoint. |
Explanation | The class is not processed for annotation metadata. |
Action | Ensure that the class file is valid and not corrupted. |
Explanation | The service reference does not have an assigned type. This does not affect the capability of the service reference. |
Action | Ensure that the service interface class file is valid and not corrupted. |
Explanation | A Web services cache is not available to the application. This will not affect the functionality of the application. |
Action | No action is required. |
Explanation | Module may not be web enabled to require a context-root. |
Action | Make sure module is web enabled. Otherwise, context-root cannot be retrieved for this module. |
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 following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: 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 following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The endpoints being started are already in the started state. |
Action | There is no need to start endpoints that are already started. |
Explanation | The endpoints being stopped are already in the stopped state. |
Action | There is no need to stop endpoints that are already stopped. |
Explanation | The service being started is already in the started state. |
Action | There is no need to start a service that is already started. |
Explanation | The service being stopped is already in the stopped state. |
Action | There is no need to stop a service that is already stopped. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | The current user does not have the required authority to invoke the Endpoint Manager MBean operation. |
Action | Log in as a user that has at least the monitor level of authority to invoke the Endpoint Manager MBean operation. |
Explanation | The current user does not have the required authority to invoke the Endpoint Manager MBean operation. |
Action | Log in as a user that has at least the operator or deployer level of authority to invoke the Endpoint Manager MBean operation. |