Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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:
garyrussell
No branches or pull requests
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: