There is no programatic way to detect if a tcp server is failed. If creating a load balancer ontop of dhcp addresses you can lose your address temporarily (and have it renewed), or permanently. It would be nice if the server indicated that it was faulted.

I think it is reasonable if there needs to be a tear down and a recreation of the server. However I would like a signal indicating that it is necessary to do so.

In the below code you can see that the go routine exits without signaling failure (it does log).

In my scenario this is related to #246 , however one could easily have the same issue when communicating to the server via rest.