TCP reader should not necessarily terminate after sender disconnects
Currently, the TcpReaderStage
terminates if the connection to its corresponding TCP writer has been closed.
This happens when the TCP writer closes the connection actively as well as the monitoring crashes or the connection is broken for other reasons.
It would be useful, if one could choose whether the stage terminates or goes to its initial state and waits for a new sender.
Maybe this is also related to TeeTime.