search cancel

What causes U00003413 Socket call 'send(221)' returned error code '104'. messages in Automation Engine log .

book

Article ID: 257354

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Customer experiences lots of Messages as below in Automation Engine logs.

20221128/000035.964 -  U00003413 Socket call 'send(221)' returned error code '104'.
20221128/000035.964 -           Connection reset by peer
20221128/000035.968 -  U00003413 Socket call 'send(221)' returned error code '32'.
20221128/000035.968 -           Broken pipe

What causes U00003413 Socket call 'send(221)' returned error code '104'. messages in Automation Engine log . 

 

Environment

Release : 12.3.4

Resolution

If the Logs has many messages as below. 

20221128/000035.964 -  U00003413 Socket-Aufruf 'send(221)' ergab Fehlercode '104'.
20221128/000035.964 -           Connection reset by peer
20221128/000035.968 -  U00003413 Socket-Aufruf 'send(221)' ergab Fehlercode '32'.
20221128/000035.968 -           Broken pipe

These messages are due to the size of the TCP/IP Message Buffer within the operating system is too small for the needs of the Automation Engine environment.
Change TCP/IP Message Buffer from 128kB to 4MB.

Linux Environments

Set the following parameters:
 
net.core.rmem_max = 4194304
net.core.wmem_max = 4194304
net.core.rmem_default = 262144
net.core.wmem_default = 262144
net.ipv4.tcp_mem = 4194304 4194304 4194304
net.ipv4.tcp_wmem = 4096 262144 4194304
net.ipv4.tcp_rmem = 4096 262144 4194304