You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Ufuk Celebi (JIRA)" <ji...@apache.org> on 2014/06/25 12:10:24 UTC

[jira] [Resolved] (FLINK-949) ChannelManager startup exception not reported in TaskManager

     [ https://issues.apache.org/jira/browse/FLINK-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ufuk Celebi resolved FLINK-949.
-------------------------------

    Resolution: Fixed

Fixed in 3d6cc5f48dc5a0336f8afdd35f59f1ee25357766.

> ChannelManager startup exception not reported in TaskManager
> ------------------------------------------------------------
>
>                 Key: FLINK-949
>                 URL: https://issues.apache.org/jira/browse/FLINK-949
>             Project: Flink
>          Issue Type: Bug
>    Affects Versions: pre-apache-0.5.1
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>
> While debugging a problem with [~rmetzger], we noticded that exception in the constructor of the {{ChannelManager}} are not properly forwarded to the {{TaskManager}}.
> The concrete problem was the following: num network buffers was misconfigured and tried to allocate more memory than available on the machine. The respective exception was hiden in the stdout file instead of the log.



--
This message was sent by Atlassian JIRA
(v6.2#6252)