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 2016/08/19 21:35:21 UTC

[jira] [Resolved] (FLINK-4403) RPC proxy classloading should use Flink class' classloader

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

Stephan Ewen resolved FLINK-4403.
---------------------------------
    Resolution: Fixed

Merged to flip-6 branch in b7259d617bbb080e486ae91aaf3d9b24addb352c

> RPC proxy classloading should use Flink class' classloader
> ----------------------------------------------------------
>
>                 Key: FLINK-4403
>                 URL: https://issues.apache.org/jira/browse/FLINK-4403
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Distributed Coordination
>         Environment: FLIP-6 feature branch
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>             Fix For: 1.2.0
>
>
> The RPC service's proxies use the {{ClassLoader.getSystemClassLoader()}} for all reflective classloading.
> In settings where Flink runs embedded, the Flink framework classes may not be in the System classloader, but for example in the classloader of an OSGI bundle. It is hence better to use the classloader of a Flink Framework class. In most cases, that will be the system classloader, in other cases it will be the classloader for the Flink code bundle: {{RpcService.class.getClassLoader()}}.



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