[jira] [Resolved] (EAGLE-719) configuration bug in applications

["Michael Wu (JIRA)" <ji...@apache.org>]

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

Michael Wu resolved EAGLE-719.
------------------------------
    Resolution: Fixed

> configuration bug in applications
> ---------------------------------
>
>                 Key: EAGLE-719
>                 URL: https://issues.apache.org/jira/browse/EAGLE-719
>             Project: Eagle
>          Issue Type: Bug
>    Affects Versions: v0.5.0
>            Reporter: wujinhu
>            Assignee: Michael Wu
>             Fix For: v0.5.0
>
>
> In eagle-hadoop-queue/eagle-jpm-mr-history/eagle-jpm-mr-running/eagle-jpm-spark-history/eagle-jpm-aggregation applications, there is an xxxAppConfig class in each application. But they have a static member like manager, which could not initialize twice
> --------------------------------------------------------------------
> public static xxxxConfig getInstance(Config config) {
>         if (config != null && manager.config == null) {
>             manager.init(config);
>         }
>         return manager;
>     }
> --------------------------------------------------------------------
> But we have many sites in production,  and will call method getInstance many times. So it will cause we may get the configuration of first site for remaining sites.



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