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

Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2014/10/03 18:26:35 UTC

[jira] [Resolved] (FLINK-1134) On the client side, the JVM does not terminate using RemoteCollectorOutputFormat

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

Stephan Ewen resolved FLINK-1134.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 0.7-incubating

Fixed via a0057f9d8803be938959be55a826440ea130ac79

Thanks for the patch!

> On the client side, the JVM does not terminate using RemoteCollectorOutputFormat
> --------------------------------------------------------------------------------
>
>                 Key: FLINK-1134
>                 URL: https://issues.apache.org/jira/browse/FLINK-1134
>             Project: Flink
>          Issue Type: Bug
>          Components: Java API
>    Affects Versions: 0.6-incubating
>            Reporter: Fabian Tschirschnitz
>            Assignee: Fabian Tschirschnitz
>            Priority: Trivial
>             Fix For: 0.7-incubating
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The client program does not shutdown after executing a job, because the threads spawned by JAVA RMI prevent it from doing so. The reason is the missing unbind() and UnicastRemoteObject.unexportObject() for the exported collector objects.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)