XCOMU0812I, XCOMU0780E, XCOMU0818I fills xcom.log file
Article ID: 141092
Updated On:
Products
Issue/Introduction
The message sequence below is repeated in the xcom.log file every few seconds when no transfers are executing and they are filling up the log.
What is the root cause of the messages?
2019/11/25 17:10:03 TID=REMOTE PRG=xcomtcp PID=22685 IP=##.##.#.#
XCOMU0812I Remote Secure TCP/IP Connection Requested.
2019/11/25 17:10:03 TID=REMOTE PRG=xcomtcp PID=22685 IP=##.##.#.#
XCOMU0780E XCOMU0780E TcpIp 507: TXPI function failed with no error code.:
2019/11/25 17:10:03 TID= PRG=xcomtcp PID=22685 IP=
XCOMU0818I Secure TCP/IP Connection Ended.
Environment
- XCOM™ Data Transport® for UNIX/Linux PC
- XCOM™ Data Transport® for Windows
Cause
Support recreated similar symptoms in-house by executing a telnet command to the XCOM server secure port (default 8045) i.e.
Enter: telnet xcom_server_hostname 8045
Enter: Ctrl+]
Enter: q
The XCOM server xcom.log file showed messages:
2023/01/18 17:37:57 TID=REMOTE PRG=xcomtcp PID=8872 IP=##.##.#.#
XCOMU0812I Remote Secure TCP/IP Connection Requested.
2023/01/18 17:37:59 TID=REMOTE PRG=xcomtcp PID=8872 IP=##.##.#.#
XCOMU0780E XCOMU0780E TcpIp 507: TXPI function failed with no error code.:
2023/01/18 17:37:59 TID= PRG=xcomtcp PID=8872 IP=
XCOMU0818I Secure TCP/IP Connection Ended.
It was suggested that in customer's environment a Load Balancer e.g. an F5, might be sending similar pings to the secure port as a health check.
Resolution
It was confirmed that a Load Balancer was sending health check pings to the secure port which resulted in the messages. If the IP in the messages is 127.0.0.1 the root cause may still be due to a Load Balancer agent installed on the actual XCOM server.
XCOMU0780E is a valid error when targeting the XCOM secure port without a certificate. Compared to a non-secure port, connection requests on the secure port first perform an SSL handshake and then proceed for regular XCOM conversation over the SSL channel.
If parameter LOG_CONNECT_MSG is set to NO in the xcom.glb file (default is YES), the number of messages can be reduced from 3 to 1 with the error message XCOMU0780E remaining.
If a health check ping is made to the non-secure XCOM listener port (default 8044) only these connection messages are seen unless LOG_CONNECT_MSG has been set to NO in which case they are removed:
2023/01/18 17:37:48 TID=REMOTE PRG=xcomtcp PID=8864 IP=##.##.#.#
XCOMU0793I Remote TCP/IP Connection Established.
2023/01/18 17:37:50 TID= PRG=xcomtcp PID=8864 IP=
XCOMU0805I TCP/IP Connection Ended.
Additional Information
For further advice on this subject see related article: Recommended method to perform XCOM port health check pings
Feedback
