Explanation | The notification service cannot add the given notification listener to the list of listeners. |
Action | Examine the underlying exception for more details and resolutions. |
Explanation | The notification service cannot remove the given notification listener from the list of listeners. |
Action | Examine the underlying exception for more details and resolutions. |
Explanation | The request cannot be performed because no matching listener is found. |
Action | Verify that the requested listener exists. |
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 | A problem occurred sending notifications to an external process. |
Action | Examine the underlying exception for more details and resolutions. |
Explanation | If a notification listener does not return from handleNotification() within a specified amount of time, it is automatically removed. |
Action | Examine the specified notification listener to see what is causing the delay. Alternatively, modify the timeout by setting the System property |
Explanation | The handleNotification() method from the specified listener threw an unhandled exception. |
Action | Examine the underlying exception for more details and resolutions. |
Explanation | The javax.management.Notification class defines a source of type 'Object', however the WebSphere notification service only allows sources of type ObjectName, as recommended by the JMX specification. |
Action | Contact the originator of the notification and suggest the use of an ObjectName as the source of this notification |
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/. |