Netty producer keeps sending message to the closed channel.

From the conversation with willem.jiang

I can tell it's an issue of netty-http.
As the back end server connection header is close, which means the back end server closes the connection after sending the response back, but netty http never close the connection if the request connection header is keep-alive. It can cause netty http producer keep sending message to channel which is closed by the back end server.

The workaround could be set the disconnect option to be true to tell netty-http producer to close the channel after it receive the response.

from("xxx").to("netty:xxx?disconnection=true").

Please feel free to create a JIRA for it, I will updated netty-http code to check the response message header to decide if the netty channel need to be closed.