Spring/spring-integration
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

INT-3912: TCP Server Listening Event

Browse Source 
JIRA: https://jira.spring.io/browse/INT-3912

Polishing - PR Comments
This commit is contained in:
Gary Russell
2015-12-14 18:03:45 -05:00
committed by Artem Bilan
parent 471d08250d
commit 180ada63b0
9 changed files with 133 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/reference/asciidoc/ip.adoc
View File

@@ -405,6 +405,14 @@ collaborating outbound channel adapter) receives a message that cannot be routed
Outbound gateways also publish this event when a late reply is received (the sender thread has timed out).
The event contains the connection id as well as an exception in the `cause` property that contains the failed message.
Starting with _version 4.3_, a `TcpConnectionServerListeningEvent` is emitted when a server connection factory is started.
This is useful when the factory is configured to listen on port 0, meaning that the operating system chooses the port.
It can also be used instead of polling `isListening()`, if you need to wait before starting some other process that will
connect to the socket.
IMPORTANT: To avoid delaying the listening thread from accepting connections, the event is published on a separate
thread.
[[tcp-adapters]]
=== TCP Adapters

5
src/reference/asciidoc/whats-new.adoc
View File

@@ -38,3 +38,8 @@ See <<jms-header-mapping>> for more information.
There is a change in behavior when a POJO aggregator releases a collection of `Message<?>` objects; this is rare but if
your application does that, you will need to make a small change to your POJO. See this <<agg-message-collection>> note
for more information.
==== TCP Changes
A new `TcpConnectionServerListeningEvent` is emitted when a server connection factory is started.
See <<tcp-events>> for more information.