[
https://issues.apache.org/jira/browse/OOZIE-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mona Chitnis updated OOZIE-1932:
--------------------------------
Attachment: OOZIE-1932-addendum.patch
attaching simple change to initialize CallableQueueService at the very end so
that its destroyed first in order. unit test TestBulkMonitorWebServiceAPI
failed in my local machine but not able to determine if cause related to this
change. I will let the pre-commit build test run decide
> Services should load CallableQueueService after MemoryLocksService
> ------------------------------------------------------------------
>
> Key: OOZIE-1932
> URL: https://issues.apache.org/jira/browse/OOZIE-1932
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Fix For: 4.1.0
>
> Attachments: OOZIE-1932-2.patch, OOZIE-1932-addendum.patch,
> OOZIE-1932.patch
>
>
> This is not a problem during startup but is during shutdown, as services are
> destroyed in reverse order of initialization. Hence, when MemoryLocksService
> destroy sets it to null, and commands are still executing due to
> CallableQueueService still active, they all encounter NPEs during locking.
> This is a simple fix in oozie-default.xml to set MemoryLocksService before in
> the order of services loading.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
