Error handling and logging

The connector logs an error message whenever it encounters a condition that causes its current processing of a business object and verb to fail. 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 connector log file or the standard output stream, depending on its configuration. You can use the text as an aid in determining the source of the error.

Error types

Table 13 describes the types of tracing messages that the connector outputs at each trace level. These messages are in addition to any tracing messages output by the IBM WebSphere Business Integration Adapter architecture, such as the Java connector execution wrapper and the WebSphere MQ message interface.

Table 13. Connector tracing messages

Tracing level Tracing messages
Level 0 Message that identifies the connector version. No other tracing is done at this level. This is the default value.
Level 1
  • Status messages
  • Messages that provide identifying (key) information for each business object processed
  • Messages delivered each time the pollForEvents method is executed

Level 2
  • Business object handler messages that contain information such as the arrays and child business objects that the connector encounters or retrieves during the processing of a business object
  • Messages logged each time a business object is posted to the integration broker, either from gotApplEvent() or executeCollaboration()
  • Messages that indicate that a business object has been received as an integration broker request

Level 3
  • Foreign key processing messages that contain such information as when the connector has found or has set a foreign key in a business object
  • Messages that provide information about business object processing. For example, these messages are delivered when the connector finds a match between business objects, or finds a business object in an array of child business objects

Level 4
  • Application-specific information messages, for example, messages showing the values returned by the functions that parse the business object's application-specific information fields
  • Messages that identify when the connector enters or exits a function, which helps trace the process flow of the connector
  • All thread-specific messages. If the connector spawns multiple threads, a message appears for the creation of each new thread

Level 5
  • Messages that indicate connector initialization, for example, messages showing the value of each configuration property retrieved from the integration broker
  • Messages that include statements executed in the application. At this trace level, the connector log file contains all statements executed in the destination application and the value of any variables that are substituted.
  • Messages that comprise a representation of a business object before the connector begins processing it (displaying its state as the connector receives it) and after the connector has completed its processing (displaying its state as the connector returns it)
  • Messages that comprise a business object dump
  • Messages that indicate the status of each thread the connector spawns while it is running

Error messages

Connector message file

All the error messages that the connector generates are stored in a message file named JDBCConnector.txt or JDBCConnector_II_TT.txt (where ll specifies a language, and TT specifies a country or territory). Each error has an error number followed by the error message. For example:

20017
Connector Infrastructure version does not match.

20018
Connection from {1} to the Application is lost! Please enter 'q' 
to stop the connector, then restart it after the problem is fixed.

20019
Error: ev_id is NULL in pollForEvent().

Copyright IBM Corp. 1997, 2004