TCP application logging errors when listen backlog has overflowed

Issue

• Abi Nitio application recording numerous "broken pipe" and "flow: Connection timed out" errors
• Packet tracing shows that after the connection is established the Abi Nitio application sends data which is not acknowledged. It then resets the connection.
• Packet tracing also shows that the RHEL server continues to respond with SYN-ACK segments, never acknowledging the data from client or even that the client is acknowledging the SYN-ACK response.