Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-6533

File.deleteOnExit should be called only when file can't be deleted

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Neutral Neutral
    • 5.4.5
    • 5.4.2
    • None
    • None
    • deleteOnExit

      We got our hand on a heapDump last week and we found that most of the memory where occupy by a large map hold by "java.io.DeleteOnExitHook" that is referencing temporary files created by Magnolia (about 200 000 references)

      This problem is referenced in sereral threads (http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6664633, http://bugs.java.com/bugdatabase/view_bug.do?bug_id=4872014, http://bugs.java.com/bugdatabase/view_bug.do?bug_id=4809375)

      We are going to correct this problem by removing the deleteOnExit call on the temp file.
      Find the usages and create tickets in corresponding modules (currently used in activation, dam, CTS...).

        Acceptance criteria

              Unassigned Unassigned
              nbarithel Nicolas Barithel
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: