You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a serializer nagles algorithm (buffering in socket) only applies to writes subsequent to the first one. Thus the first write is sent as a single TCP packet, regardless of length.
Sending a BufferedOutputStream to the serializer should help.
Dennis Thrysøe opened INT-3507 and commented
In a serializer nagles algorithm (buffering in socket) only applies to writes subsequent to the first one. Thus the first write is sent as a single TCP packet, regardless of length.
Sending a BufferedOutputStream to the serializer should help.
Affects: 3.0 GA
Reference URL: http://stackoverflow.com/questions/25551261/java-spring-integration-tcp-flush-control
Issue Links:
Referenced from: pull request #1268
The text was updated successfully, but these errors were encountered: