Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-1932

Services should load CallableQueueService after MemoryLocksService

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • trunk
    • 4.1.0
    • None
    • None

    Description

      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.

      Attachments

        1. OOZIE-1932.patch
          3 kB
          Mona Chitnis
        2. OOZIE-1932-2.patch
          1.0 kB
          Mona Chitnis
        3. OOZIE-1932-3.patch
          1 kB
          Mona Chitnis
        4. OOZIE-1932-4.patch
          1 kB
          Mona Chitnis
        5. OOZIE-1932-4-amendment.patch
          0.8 kB
          Mona Chitnis
        6. OOZIE-1932-addendum.patch
          1 kB
          Mona Chitnis

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. OOZIE-2054 SharelibService hits NullPointerException when server starts

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              chitnis Mona Chitnis
              chitnis Mona Chitnis
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: