[
https://issues.apache.org/jira/browse/FLINK-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347461#comment-14347461
]
ASF GitHub Bot commented on FLINK-1650:
---------------------------------------
GitHub user StephanEwen opened a pull request:
https://github.com/apache/flink/pull/455
[FLINK-1650] [logging] Suppress wrong netty warnings on akka shutdown
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/StephanEwen/incubator-flink
netty_error_message
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/455.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #455
----
commit 877f87f65b0179341081adda20081a818eaffaf3
Author: Stephan Ewen <se...@apache.org>
Date: 2015-03-04T19:52:50Z
[FLINK-1650] [logging] Suppress wrong netty warnings on akka shutdown
----
> 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)
