[
https://issues.apache.org/jira/browse/OOZIE-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1823:
---------------------------------
Attachment: OOZIE-1823.patch
The patch simply sets {{oozie.services.ext}} to an empty String before initing
the Services so it won't load any ext services. No test because it's a pretty
trivial change; but I did verify that it fixes the problem.
> OozieSharelibCLI shouldn't load ext services
> --------------------------------------------
>
> Key: OOZIE-1823
> URL: https://issues.apache.org/jira/browse/OOZIE-1823
> Project: Oozie
> Issue Type: Bug
> Components: tools
> Affects Versions: 4.0.1
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Blocker
> Attachments: OOZIE-1823.patch
>
>
> OozieSharelibCLI (invoked via running {{oozie-setup.sh sharelib}} commands)
> should not load the ext services (i.e. {{oozie.services.ext}}). This is
> unnecessary and can even lead to problems. For example, if you enable
> JMS/SLA messaging, you'll add the EventHandlerService which will get loaded
> when you run OozieSharelibCLI; however, this will fail because
> OozieSharelibCLI doesn't load the SchedulerService, which EventHandlerService
> tries to use and you get an NullPointerException. This prevents anyone who
> is using this feature from (easily) updating their sharelib.
> This isn't a problem for OozieDBCLI even though it uses Services because it
> doesn't actually {{init()}} them.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
