Oh. If so, should camel-netty4 sync=true be taken into consideration for the fix?
Just wondering, mine is sync=false though. And thank you for the (very quick) fix! From: Claus Ibsen Sent: Wednesday, 3 January, 2018 4:40 PM To: [email protected] Hi Yeah you are right, we should try to fix this. The trick is that the camel-netty4-http would rely on returning HTTP status codes when shutting down and not kill the tcp socket listener etc, as plain camel-netty4 would do. On Wed, Dec 27, 2017 at 4:17 PM, <[email protected]> wrote: > Hi, > > > > > So, I'm using this URI: `netty4:tcp://localhost:8888?sync=false&textline=true` > > > I have this issue when initiating Camel shutdown using > `DefaultShutdownStrategy`: > > > 1. Camel suspends `NettyConsumer` (`SingleTCPNettyServerBootstrapFactory`), > which only stops the "main" Netty channel, but _not_ the other Netty channels > (i.e. socket connections) > 2. Camel waits for routes to be empty of inflight & pending exchanges > 3. (!) Those other Netty channels kept receiving data, which are turned into > new exchanges > ** As long as the TCP clients keep sending data into the channels + exchanges > completing slower than send rate, routes will _never_ be empty of inflight & > pending exchanges > 4. Forced shutdown after 5 minutes (timed out) > > > I have some scripts to simulate the issue - they are in > https://issues.apache.org/jira/browse/CAMEL-12103. > > > Did I configure (or didn’t configure) something wrongly, or this is a bug? > > > p/s: Sorry for the faux pas of creating a ticket before sending an email here. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
