[EAGLE-719] configuration bug in applications

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: v0.5.0
• Fix Version/s: v0.5.0
• Assignee: Michael Wu
• Reporter: wujinhu
• Created: 02/Nov/16 02:27
• Updated: 16/Nov/16 03:05
• Resolved: 02/Nov/16 10:59

Description

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.

Issue Links

• links to: GitHub Pull Request #598