IBM Support

IV54704: LOCK FILES CREATED BY FILEHANDLER NOT GETTING CLEANED-UP WITH GC

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: The lock files are not getting closed if
    FileHandler.close() is not called explicitly. As a result, if
    new FileHandler with the same file name is constructed, the file
    name is regarded as unusable.
    .
    Stack Trace: N/A
    .
    N/A
    

Local fix

  • N/A
    

Problem summary

  • The finalizer is not taking care of closing the file descriptor
    of the FileHandler if not explicitly close it.
    

Problem conclusion

  • This defect will be fixed in:
    7.0.0 SR7
    7.1.0 SR1
    .
    The JDK has been updated to close the file descriptor from the
    finalize method of FileHandler.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV54704

  • Reported component name

    JAVA CLASS LIBS

  • Reported component ID

    620700130

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-01-28

  • Closed date

    2014-02-27

  • Last modified date

    2014-02-27

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    JAVA CLASS LIBS

  • Fixed component ID

    620700130

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
21 February 2022