[jira] [Commented] (APEXCORE-740) Setup plugins does not identify operator classes because they're loaded through different classloaders

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (APEXCORE-740) Setup plugins does not identify operator classes because they're loaded through different classloaders

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/APEXCORE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036569#comment-16036569 ]

Chinmay Kolhatkar commented on APEXCORE-740:
--------------------------------------------

RCA:
StramAppLauncher.loadDependencies is getting called multiple times. This method loads the new jars in apa and adds to the thread context class loader. The issue is that it just overrides the parent class loader. It should rather build over the parent/existing. Hence each time loadDependencies is called, same classes gets loaded and becomes part of seperate class loader.
Now the order of execution happens this way: loadDependencies(), load setup plugin, loadDependencies(), load operator classes. These operator classes are different classes as compared to one which setup plugin understands.

> Setup plugins does not identify operator classes because they're loaded through different classloaders
> ------------------------------------------------------------------------------------------------------
>
>                 Key: APEXCORE-740
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-740
>             Project: Apache Apex Core
>          Issue Type: Bug
>            Reporter: Chinmay Kolhatkar
>            Assignee: Chinmay Kolhatkar
>
> Apexcli loads setup plugin and operator classes with different thread context class loader. Because of this, the setup plugin does not understand the operator classes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)