Oracle Web Services On Demand Guide > Best Practices for Designing Client Application > Best Practices for Integration Performance >

Handling Bad Events in Integration Event Queues

Sometimes an integration event queue might contain an event that the client application cannot process. This situation can occur, for example, if a new custom field has been flagged as required but the client application that processes integration events has not been updated with a schema file that includes the integration tag for the new custom field.

Client applications cannot selectively delete events from the queue, so they must handle these events by performing the following steps:

1. In the GetEvents call, reduce the number of events retrieved by setting the EventCount argument to 1.
2. Use GetEvents to retrieve single events and process each of them until a bad event is identified.
3. If a parse error is encountered, save the bad event to a local folder or other location.
4. Delete the bad event from the queue using a DeleteEvents call with the LastEventId argument set to the ID of the bad event.
5. Continue processing events with the number of events set back to the default value.
6. Repeat steps 1 through 5 if more bad events are encountered.

For information about GetEvents and DeleteEvents, see GetEvents, and DeleteEvents respectively.