On further investigation, I see that the *closeChannelTimeMillis* option is not a *netty *option, but rather an option for com.linkedin.norbert.javacompat.network.NetworkClientConfig <http://grepcode.com/file/repo1.maven.org/maven2/com.linkedin/norbert_2.8.1/0.6.33/com/linkedin/norbert/javacompat/network/NetworkClientConfig.java> .
The Norbert ChannelPool closing channels prematurely <https://linkedin.jira.com/browse/NOR-19> JIRA issue is still in the unresolved state. We are are facing a similar issue in production (with very similar stack traces for Norbert scenarios 2 and 3, as shown in the JIRA issue) and were hoping for a resolution to this similar issue. Any thoughts on this are appreciated. Thanks, SteveR -- View this message in context: http://camel.465427.n5.nabble.com/camel-netty-How-to-set-the-netty-closeChannelTimeMillis-option-tp5772342p5772347.html Sent from the Camel - Users mailing list archive at Nabble.com.
