[
https://issues.apache.org/jira/browse/OOZIE-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082590#comment-14082590
]
Mona Chitnis commented on OOZIE-1932:
-------------------------------------
okay thanks. will revise the order
> 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)
