Deploy the camel-netty-binding quickstart, then undeploy it. Watch the CPU max out on your machine. I took a quick look at this with jstack and a thread/CPU capture and Netty is gobbling up all the available CPU. Not sure if this is an issue with how we are shutting down the route on undeploy or if it's a bug in the underlying camel-netty component or Netty itself. I guess we could rule that out by creating a standalone Camel app deployed as a WAR and then undeploy that.