XCOM task is receiving the following messages causing the TCP/IP listener to terminate:
XCOMM0794E RECURSIVE ERROR DETECTED, TCP/IP LISTENER TERMINATED
XCOMM0780E Txpi 105: Parameter TXPI_CONNECT is NULL
Release : 12.0
Component : XCOM Data Transport for z/OS
Other messages that were observed and occurring recursively in the XCOMLOG of the task were:
XCOMM0800E ERROR ATTACHING TXPI SUBTASK
XCOMM1467I OMVS EDC8124I Socket not connected. (errno2=0x749B0000)
XCOMM0780E Txpi 234: Error 1124 from getpeername; length : 28
XCOMM0780E Txpi 701: Received remote data block at 0X1EB44504 starting with invalid EyeCatcher 0X67717737
XCOMM0780E Txpi 126: SSL handshake request received on non-secure socket
XCOMM0805I TCP/IP CONNECTION ENDED WITH IP=ipaddr
XCOMM1600E Call to BPX1GPI IBM UNIX System Service failed ( XCOMSTSK+275E )
XCOMM1601E R15=0F01C008 - An error occurred trying to dub the process as a z/OS UNIX process
XCOMM1601E R02=0000009C - EMVSINITIAL - Process Initialization error
XCOMM1601E R03=0B250012 - JRMaxChild - The MAXPROCUSER setting for this user ID has been exceeded
XCOMM1600E Call to BPX1GPI IBM UNIX System Service failed ( XCOMSTSK+275E )
XCOMM1601E R15=0F01C008 - An error occurred trying to dub the process as a z/OS UNIX process
XCOMM1601E R02=0000009C - EMVSINITIAL - Process Initialization error
XCOMM1601E R03=0B250012 - JRMaxChild - The MAXPROCUSER setting for this user ID has been exceeded
All of the above messages confirm that the messages are caused by the application scanning the port used by XCOM.
It has been determined that the scans are overloading the XCOM server. It was observed that the following messages
XCOMM1600E Call to BPX1GPI IBM UNIX System Service failed ( XCOMSTSK+275E )
XCOMM1601E R15=0F01C008 - An error occurred trying to dub the process as a z/OS UNIX process
XCOMM1601E R02=0000009C - EMVSINITIAL - Process Initialization error
XCOMM1601E R03=0B250012 - JRMaxChild - The MAXPROCUSER setting for this user ID has been exceeded
happened twice before it got an error attaching the subtask. It also showed that a scan ran for 18 minutes after the previous one ended.
It is suggested that the scanning of the port be throttled as to prevent the overload to the XCOM server. The overload can cause the XCOM listener to terminate and that would require that the task be recycled.