NetcatSource stop() function returns when client still connected to the source,
and can still write to it.
----------------------------------------------------------------------------------------------------------
Key: FLUME-1084
URL: https://issues.apache.org/jira/browse/FLUME-1084
Project: Flume
Issue Type: Bug
Components: Sinks+Sources
Reporter: Hari Shreedharan
Previous behavior(commit: 48edaf2) :
* netcat source runner.stop blocked till the accept handler exited when the nc
client connected to it closed the connection
(logs: [DEBUG -
org.apache.flume.source.NetcatSource.stop(NetcatSource.java:208)] Waiting for
handler service to stop)
New behavior(commit: 39aba18):
* netcat source runner.stop returns but a connected a client can still write to
it, while a new source started up for the same agent due to reconfiguration.
Note that a new client can startup on the same port as the old netcat source
with no bind exception.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
