CORBA 2.6.1 Programmer's Reference

Event Service Error Messages (Error numbers 2600
- 2799)
2601 - push_to_consumer got system exception when tried to 'push' exception#
User Action: The Event Service was unable to sucessfully interact with a an application provided
push consumer. The push consumer did not receive an event. The event service ceases to try to
interact with the push consumer. Verify that no unexpected error occurred in an application
provided push consumer. If the the push consumer correctly ceased to exist, no further action is
necessary. For best results, the push consumer should be be reworked to correctly disconnect from
the event channel before exiting. If the push consumer process failed, restart it and have it
reregister with the event channel.
2602 - pull_to_supplier got system exception when tried to 'pull' or 'try_pull' exception#
User Action: The Event Service was unable to sucessfully interact with an application provided
pull supplier. An event service consumer may not have obtained an event as expected. If a comm
failure exception was raised, the event service ceases to try to interact with the offending pull
supplier. Verify that no unexpected error occurred in an application provided pull supplier. If the
the pull supplier correctly ceased to exist, no further action is necessary. Otherwise, if a comm
failure occurred, the pull supplier should be restarted and reregistered with the event channel. If
there was an exception other than a comm failure, the event channel will continue to try to interact
with the pull supplier. If further errors occur, restart the pull supplier.
2603 - pull_from_supplier got user exception when tried to 'pull' or 'try_pull' exception#
User Action: This error is logged for information purposes; it has no effect on the Event Service.
In response to a pull or try_pull request, an application provided pull supplier should not
produce any user exception other than Disconnected. Rewrite the application so that it does
not generate the offending user exception.
2604 - GetEvent encountered inconsistency in saved events
User Action: An event requested by a consumer may not be available. The event channel is unable
to deliver a specific event but will recovers and deliver subsequent events.
2605 - release_proxy could not find object to be released
User Action: The event channel encountered an internal consistency problem but recovered
automatically. If this problem occurs frequently, contact your service provider
2606 - EventService could not obtain Root Name Context
User Action: The Event Service object reference was not placed in Naming Service. If this error is
not corrected, application programs will be unable to query the Naming Service for an Event
Service object reference. Verify that the configuration for Naming Service is correct. Make sure
Naming Service is operational. Verify that root name context for Naming Service appears in the
configuration database. After correcting Naming Service errors, restart the Event Service.
2608 - (ZDOM-ES-ERR-EXTRA1)