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

Option to disable OpenJPA BrokerImpl finalization

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.0
    • Component/s: None
    • Labels:
      None

      Description

      We noticed that GC is taking a long time in our production. Looking at the live objects, we can see a lot of FinalizingBrokerImpl.

        10:         33881        8402488  org.apache.openjpa.kernel.FinalizingBrokerImpl
        15:         91943        3677720  java.lang.ref.Finalizer
      1134:             1            384  java.lang.ref.Finalizer$FinalizerThread
      1672:             4            128  org.apache.hadoop.yarn.proto.YarnProtos$FinalApplicationStatusProto
      1926:             4             96  org.apache.hadoop.yarn.api.records.FinalApplicationStatus
      

      By default Broker Finalization is enable to safeguard the accidental resource leaks that may occur if a developer fails to explicitly close EntityManagers when finished. Since we are closing all EntityManagers on final block. We should not have any issue.
      More details @ http://openjpa.apache.org/builds/1.2.3/apache-openjpa/docs/ref_guide_optimization.html

        Attachments

        1. OOZIE-2542-V3.patch
          4 kB
          Purshotam Shah
        2. OOZIE-2542-V2.patch
          4 kB
          Purshotam Shah
        3. OOZIE-2542-V1.patch
          4 kB
          Purshotam Shah

          Activity

            People

            • Assignee:
              puru Purshotam Shah
              Reporter:
              puru Purshotam Shah
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: