WebSphere Process Server messages     Operating Systems: All supported

ADME

ADME0000W: The system cannot add the listener to process {0}: {1}
Problem The notification service cannot add the given notification listener to the list of listeners.
User response Examine the underlying exception for more details and resolutions.
ADME0001W: The system cannot remove the listener from process {0}: {1}
Problem The notification service cannot remove the given notification listener from the list of listeners.
User response Examine the underlying exception for more details and resolutions.
ADME0002W: The system did not find the listener to remove with information {0}
Problem The request cannot be performed because no matching listener is found.
User response Verify that the requested listener exists.
ADME0003W: The system is unable to register the notification listener to MBeanServer: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response 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/.
ADME0004W: The system cannot send notifications: {0}
Problem A problem occurred sending notifications to an external process.
User response Examine the underlying exception for more details and resolutions.
ADME0005E: The following notification listener was removed because it did not handle a notification within {0}ms: {1}
Problem If a notification listener does not return from handleNotification() within a specified amount of time, it is automatically removed.
User response Examine the specified notification listener to see what is causing the delay. Alternatively, modify the timeout by setting the System property
ADME0006W: An exception occurred sending notification {0} to {1}: {2}
Problem The handleNotification() method from the specified listener threw an unhandled exception.
User response Examine the underlying exception for more details and resolutions.
ADME0007W: The notification source is not of type ObjectName; type={0}, source={1}
Problem 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.
User response Contact the originator of the notification and suggest the use of an ObjectName as the source of this notification
ADME0008W: Unable to deliver or handle {0} notification: {1}.
Problem This exception is unexpected. The cause is not immediately known.
User response 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/.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.management.resources.event.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)