Socket send buffer size is xxx.xxx instead of the requested yyy.yyy
search cancel

Socket send buffer size is xxx.xxx instead of the requested yyy.yyy

book

Article ID: 294287

calendar_today

Updated On:

Products

VMware Tanzu Gemfire

Issue/Introduction

Symptoms:

The following info entry is observed in the server logs:

[info 2015/05/12 10:52:38.960 CDT olaxsd-itwgfdatakcg00 <poolTimer-sso_customerLogin-A-79> tid=0x5d3] Socket send buffer size is 212,992 instead of the requested 524,288.

Environment


Cause

The "Socket send buffer size is xxx instead of the requested yyy" log message is strictly informative. Basically, GemFire try to set the SO_SNDBUF option for this Socket to the socket-buffer-size. However, SO_SNDBUF is used by the platform's networking code as a hint only for the size to set the underlying network I/O buffers, so GemFire check to verify what size the buffers were actually set to and log if it is less than requested. This usually indicates that GemFire asked for more than the OS-level configured limit.

Resolution

There are three options here:

  1. Ignore the message — it’s harmless
  2. Set "socket-buffer-size” to 124,928 or less
  3. Have your system admin increase the limit at the OS-level.