You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Mona Chitnis (JIRA)" <ji...@apache.org> on 2014/07/15 17:22:05 UTC

[jira] [Created] (OOZIE-1932) Services should load CallableQueueService after MemoryLocksService

Mona Chitnis created OOZIE-1932:
-----------------------------------

             Summary: 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: trunk


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)