Bad Performance and "U0003413 Socket call 'send(31511)' returned error code '32'. Broken pipe" errors
search cancel

Bad Performance and "U0003413 Socket call 'send(31511)' returned error code '32'. Broken pipe" errors

book

Article ID: 87870

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
U0003413 Socket call 'send(31511)' returned error code '32'.
Broken pipe

If experiencing an overall degradation in the performance of the Automation Engine (AE) and are seeing the following symptoms:

  • The Performance of the system decreases in general.
  • The UI User facing bad performance or UI freezes for some minutes.
  • The automated processing seems to be not influence that much.
  • The number of records in the MQCP-Tables goes up to several thousand, the system can bring it down to a normal value for a short time. Than the number of records got up again.
In the CP logs the following Socket errors messages are issued over and over:
 
20160203/114402.109 - U0003413 Socket call 'send(31511) returned error code '32'.
20160203/114402.109 -          Broken pipe
20160203/114402.109 - U0003413 Socket call 'send(31511)' returned error code '32'.
20160203/114402.109 -          Broken pipe
...


 

Cause

Root Cause:

The size of the TCP/IP Message Buffer within the operation system is too small for the needs of the Automation Engine environment.

Resolution

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


Fix Status: No Fix

Fix Version(s):
N/A

Additional Information

Workaround :
N/A