Control-M/Server disconnects intermittently when arbitrary data is injected into any of the listen ports, such as from Security or Antivirus software.

Some symptoms seen include (but are not limited to), CE process crashing, Gateway disconnecting, Agents becoming unavailable, or failed API calls.

In the ctm_server/proclog or proclog.save directores, the p_ctmce.stdout may show the following sample message:

p_ctmce.stdout.##### :
======================

Sun Mar 06 21:38:16 EST 2022  Msg format is invalid:GET /10uTf (Hexdump: 47 45 54 20 2F 31 30 75 54 66 37 71 20 48 54 54 50 2F 31 2E 30 0D 0A 0D 0A)
Sun Mar 06 21:38:16 EST 2022  Inside ApiGtwShutdownEventHandler 0
Sun Mar 06 21:38:16 EST 2022  Inside ApiGtwShutdownEventHandler 0
2022-03-06 21:38:16.125  INFO 84933 --- [       Thread-6] o.s.s.c.ThreadPoolTaskScheduler          : Shutting down ExecutorService 'taskScheduler'

OR
Fri Dec 08 16:20:17 CST 2023 Msg format is invalid:SSH-2.0-Op (Hexdump: 53 53 48 2D 32 2E 30 2D 4F 70 65 6E 53 53 48 5F 37 2E 34 0D 0A)
Fri Dec 08 16:20:17 CST 2023 Inside ApiGtwShutdownEventHandler 0
Fri Dec 08 16:20:17 CST 2023 Inside ApiGtwShutdownEventHandler 0
Fri Dec 08 16:20:17 CST 2023 Fri Dec 08 16:20:17 CST 2023: Setting levels of logger 'com.bmc.ctms.ctminfra.protocols.agent.AgentBaseDsect' to: memory=FINEST, file=INFO
Fri Dec 08 16:20:17 CST 2023 Fri Dec 08 16:20:17 CST 2023: Failed to find memory handler for com.bmc.ctms.ctminfra.protocols.agent.AgentDsectListMsg
2023-12-08 16:20:17.810 INFO 3531 --- [    Thread-6] o.s.s.c.ThreadPoolTaskScheduler     : Shutting down ExecutorService 'taskScheduler'

-------

CTM-6625 has been created for this issue 
Install the latest available version and patch to resolve this issue :

https://docs.bmc.com/xwiki/bin/view/Control-M-Orchestration/Control-M/ctm9021/Control-M-9-0-21-300-Release-Notes/

https://docs.bmc.com/xwiki/bin/view/Control-M-Orchestration/Control-M/ctm9021/Patches/Control-M-Server-PACTV-9-0-21-302/

https://docs.bmc.com/xwiki/bin/view/Control-M-Orchestration/Control-M/ctm9021/Patches/Control-M-Server-PACTV-9-0-21-308/

Alternate option before version 9.0.21.100 for 9.0.20.200

Perform both of the following steps:

1. Install the Control-M/Server 9.0.20.211 or later patch on top of 9.0.20.200:
https://docs.bmc.com/docs/pages/viewpage.action?pageId=1152395289

2. Create rules for the scanning software to skip checking the following ports:

Port number	Description	Configuration location	Affected version
2370	Control-M/EM TCP/IP Port Number	ctm_menu->4->1	9.0.18, 9.0.19, 9.0.20, 9.0.21
2369	Configuration Agent Port	ctm_menu->4->1	9.0.18, 9.0.19, 9.0.20, 9.0.21
2368	HA Configuration Agent Port	ctm_menu->4->1	9.0.18, 9.0.19, 9.0.20, 9.0.21
7005	Agent-to-Server Port	ctm_menu->4->1	9.0.18, 9.0.19, 9.0.20, 9.0.21
8393	API Gateway Port	config.dat  parameter API_GATEWAY_PORT	9.0.20, 9.0.21
6005 local	IPC port	ctm_menu	9.0.18, 9.0.19, 9.0.20, 9.0.21
12181	Kafka Port	services.yml	9.0.20, 9.0.21
dynamic	CE API Port	api_gateway_url.dat	9.0.21
dynamic	MS Order Service	ctms-order-service.yml	9.0.21
dynamic	MS App Update	ctms-app-updates-service.yml	9.0.21
dynamic	MS Job Info Service	ctms-job-info-service.yml	9.0.21
19092	Zookeeper Port	services.yml	9.0.20, 9.0.21

The API Gateway default port is dynamic unless defined in ctm_server/data/config.dat.
The parameter API_GATEWAY_PORT can be added to config.dat to define one free port.
if the default port is in use a new one will be allocated.

All ports listed are default values. Use the "Configuration location" column to verify the current values and use those to prevent port scanning.

MicroServices (MS) configuration files are found in ~/ctm_server/services/context folder. "server.port" identifies the port that will be assigned. A value of 0 is dynamic.

Additional Information regarding Step 2:
As a stop-gap measure, you can disable the Security scanning software