[ https://issues.apache.org/jira/browse/FLINK-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348521#comment-14348521 ]
ASF GitHub Bot commented on FLINK-1650: --------------------------------------- Github user uce commented on the pull request: https://github.com/apache/flink/pull/455#issuecomment-77337668 +1, as well. I agree with Till regarding the log4j-test file. If you add it there as well, don't forget to add it to `tools/log4j-travis.log` as well. > Suppress Akka's Netty Shutdown Errors through the log config > ------------------------------------------------------------ > > Key: FLINK-1650 > URL: https://issues.apache.org/jira/browse/FLINK-1650 > Project: Flink > Issue Type: Bug > Components: other > Affects Versions: 0.9 > Reporter: Stephan Ewen > Assignee: Stephan Ewen > Fix For: 0.9 > > > I suggest to set the logging for > `org.jboss.netty.channel.DefaultChannelPipeline` to error, in order to get > rid of the misleading stack trace caused by an akka/netty hickup on shutdown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)