Constant errors LCOT000I and LCOA007I in IBM Sterling Connect:Direct statistics log file

Technote (troubleshooting)


Problem(Abstract)

Constant errors LCOT000I and LCOA007I in IBM Sterling Connect:Direct statistics log file. Load Balancing is being used to probe the IBM Sterling Connect:Direct port numbers.

Symptom

The following are errors in statistics log file:

LCOT000I
The comm thread termination has started.
API connection comm channel <IP address> failed with LCOA007I

LCOA007I
Comm thread failed to get sessinfo exchanged with the client.

&ERC=0,&EFDBK=8,&ETXT=No_substitution_text)


Environment

IBM Sterling Connect:Direct Windows

Resolving the problem

You can not prevent a load balancer from probing these ports and generating the errors; It is the way that IBM Sterling Connect:Direct works that when a connection is established it expects a
valid Connect:Direct handshake to follow. If the Load Balance does not follow the session establishment with a valid Connect:Direct (C:D) handshake, a message a error will be generated. We suggested using 1363 instead of 1364 as it will reduce the amount of messages, but not stop them completely.
The IBM Sterling Secure Proxy (SSP) product, offers the solution to remove the messages completely. The way to do it is to place a SSP Adapter in front of the C:D server and probe that device instead. SSP supports probes to a HTTP port so no error messages will be generated on the backend of C:D servers.

Rate this page:

(0 users)Average rating

Document information


More support for:

Sterling Connect:Direct
Performance

Software version:

4.4.1, 4.5, 4.5.1, 4.6

Operating system(s):

Windows

Reference #:

1633666

Modified date:

2013-04-09

Translate my page

Machine Translation

Content navigation