The connector logs any abnormal condition that it encounters during processing, regardless of the trace level. It writes the error text to the connector log file; the name and location of this file are set by the LogFileName connector configuration property.
The message contains a detailed description of the condition and the outcome and may also include extra information that may aid in debugging, such as business object dumps or stack traces (for exceptions).
For a complete list of error messages, refer to the
BIA_TCPIPConnector.txt message file installed in the
ProductDir\connectors\messages directory. Table 4describes some of more common errors and how
the connector handles those errors.
Error description | Error type | Error handling | Steps to correct |
---|---|---|---|
Mandatory CFG properties not populated | Fatal | Error logged and connector terminates | Make sure properties are populated |
Pre-requisite BO definitions not in repository | Fatal | Error logged and connector terminates | Make sure all .xsd files are in the repository |
Only Client or only Server is configured in CFG | Warning | Warning logged and the connector processes only requests or events, respectively | If both functions are desired, make sure all properties in CFG are configured |
CFG properties are of inappropriate type, e.g. negative values where positive are required | Fatal | Error logged and connector terminates | Make sure properties are of the appropriate type |
Server that is configured for requests not available | Error | The request fails, but the connector does not terminate | Make sure a)
application server is running and b) remote host is available from connector machine |
Socket on server configured for request times out before request sent. | Error | Socket closure error logged. Connector continues. Failure status sent to broker. | See above |
Socket closes before complete event is received | Error | Error logged, and connector continues | Do not close socket immediately after sending data to the connector |
Bind exception trying to bind socket to local port | Fatal | Error logged, and connector terminates | Make sure port is free |
Maps specified in map MO missing | Error | Error logged, and connector terminates | Make sure map .xsd files available in repository |
PIMO level error | Error | PIMO infrastructure logs error and connector terminates | Make sure that the maps and the related action are configured properly |