When an error has occurred, the adapter writes an error record to the error log. To investigate the error, review the error log and locate the particular log message to determine where processing failed and the event status at the time of failure. To examine event contents, you must find the record in the file event store. Most error records that indicate a failure has occurred are located in the archive with status FAIL, that is a file exists ending with the characters _3 in the file name. Some records might still be in the event store directory with an error status (file ending with a negative number). To examine the file contents, find the log message that correlates the event ID with the event record file name:
(wbix_transport_msg0023=Translating eventID {0} to record name {1}).
Then examine the record file to see the event contents that caused the error.
The actions you take for a failed event are different depending on the event type and customer situation. However, a failed event can often be recovered and resubmitted to the hub.
Use the transaction data in the event store to understand the failure. It is not recommended that you manually resubmit the data to the adapter. Events should be recovered either by setting the InDoubtEvents standard connector property in the adapter or through the target application that originated the event.
You can resubmit failed events from the IndusConnect Framework in two ways. The preferred method is to re-edit the object in the Indus PassPort application so that it is republished by the IndusConnect Framework. The second method is by resetting the event status to PrePollStatus in the external event store table so that the event is processed by the adapter in the next poll.
The archive contains information on all events, both successful and failed. The exception to this rule are events with duplicated IDs. Only the first event of a specific status is archived. Therefore, if an event enters the adapter with ID 123 and another event with the ID 123 is sent in before the first event is sent to the broker, the archive contains two records: one record for the successful event and a second record for the failed duplicate. These will be the only two events in the archive even if more events with the same ID are sent. Error messages for the successive events continue to be written to the log however.
Error records have the following format:
[timestamp][system][component][thread label][error message: error exception: errorexception message]
The following is a sample error which maps to the previous format:
[Time: 2003/06/25 15:37:05.715] [System: ConnectorAgent] [SS: IndusConnector] [Thread: Indus.IndusSenderReceiver (#6276108)] Unable to extract events from HTTP store: com.ibm.wbix.adapter.transports.http.HTTPTransportException: XML parsing failed: org.xml.sax.SAXParseException: The element type "MRAccounting" must be terminated by the matching end-tag " </MRAccounting>"