Issue

A Camel route running on Fuse accepts input from HTTP clients, using camel-netty-http as a consumer. When the Camel route is shut down administratively, but the Fuse server remains running, we observe that the HTTP endpoint will still accept connections. External monitoring systems that assume that the ability to establish a TCP connection to the socket is an indicator of health can mislead the administrator into thinking that the route is running, when it is not.