Logging error messages

Logging messages provides a history of events and actions taken by components.The Retek connector will log a message automatically whenever it encounters an abnormal condition during processing, regardless of the trace level.

When such an error occurs, the connector also prints a textual representation of the failed business object as it was received. It writes the text to the message file, RetekConnector.txt,indicated by the Message File Name standard property. The message contains a detailed description of the condition and the outcome and may also include extra information that may aid in debugging.

Error types: Error messages are of three types:

Error handling

The following table classifies and describes event and request processing errors and how the connector handles them.

Error description Error type Handling by connector
Connection lost while polling Fatal error The connector detects the connection error at the time of a poll call and shuts down. It logs a fatal error and sends a return code of APPRESPONSE_TIMEOUT so that e-mail notification can be triggered.
Connection lost on request processing Fatal error The connector detects the connection error when processing a business object service call request and shuts down. It logs a fatal error and sends the return code of APPRESPONSE_TIMEOUT so that e-mail notification can be triggered.
GETNXT failure Error The transaction is rolled back, and an error is logged. The connector will retry to retrieve the message up to a configurable number of times, after which administrative intervention is necessary to fix the problem.
Event not subscribed Warning The transaction is committed, a warning is logged, and the event is marked with an "Unsubscribed" status.
gotApplEvent failure Error The error is logged and the event is marked with an "Error" status.
CONSUME failure Error The connector will roll back the transaction, log an error, and return CWConnectorConstants.FAIL to the collaboration object/flow, which is responsible for any retry logic.

Copyright IBM Corp. 1997, 2003