[
https://issues.apache.org/jira/browse/FLINK-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861285#comment-15861285
]
ASF GitHub Bot commented on FLINK-5745:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3293
Looking at this and at my previous pull request, I am wondering if we
should actually define and collect exit codes somewhere globally, like in
`flink-core:org.apache.flink.configuration.ExitCodes`.
> Set uncaught exception handler for Netty threads
> ------------------------------------------------
>
> Key: FLINK-5745
> URL: https://issues.apache.org/jira/browse/FLINK-5745
> Project: Flink
> Issue Type: Improvement
> Components: Network
> Reporter: Ufuk Celebi
> Priority: Minor
>
> We pass a thread factory for the Netty event loop threads (see
> {{NettyServer}} and {{NettyClient}}), but don't set an uncaught exception
> handler. Let's add a JVM terminating handler that exits the process in cause
> of fatal errors.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
