GH-2837: TCP NIO Prioritize accept
See https://github.com/spring-projects/spring-integration/pull/2837 Give priority to accepting new connections over reading data from existing connections. Add a flag to allow users to revert to the previous behavior of giving reads priority. **cherry-pick to 5.1.x** # Conflicts: # spring-integration-ip/src/main/java/org/springframework/integration/ip/tcp/connection/TcpNioServerConnectionFactory.java # src/reference/asciidoc/whats-new.adoc # TcpNioConnectionTests.java
This commit is contained in:
committed by
Artem Bilan
parent
6e9bb60a61
commit
6f3fd0961f
@@ -971,6 +971,10 @@ Alternatively, you can insert a resequencer downstream of the inbound endpoint t
|
||||
If you set `apply-sequence` to `true` on the connection factory, messages arriving on a TCP connection have `sequenceNumber` and `correlationId` headers set.
|
||||
The resequencer uses these headers to return the messages to their proper sequence.
|
||||
|
||||
IMPORTANT: Starting with version 5.1.4, priority is given to accepting new connections over reading from existing connections.
|
||||
This should, generally, have little impact unless you have a very high rate of new incoming connections.
|
||||
If you wish to revert to the previous behavior of giving reads priority, set the `multiAccept` property on the `TcpNioServerConnectionFactory` to `false`.
|
||||
|
||||
==== Pool Size
|
||||
|
||||
The pool size attribute is no longer used.
|
||||
|
||||
Reference in New Issue
Block a user