Status/Resolution/Reason: Closed/Withdrawn/Duplicate
Reporter/Name(from Bugbase): Michael Littleton / Michael Littleton (Michael Littleton)
Created: 10/13/2015
Components: Database
Versions: 10.0
Failure Type: Memory Leak
Found In Build/Fixed In Build: Final /
Priority/Frequency: Trivial / Unknown
Locale/System: English / Win 2008 Server R2 64 bit
Vote Count: 0
Duplicate ID:	CF-4038087
Problem Description:
On a long running server, memory will continue to be consumed by the "deleteonexithook" in java.  Upon heap dump, this will contain millions of records to non-existent files that match this pattern: ddtb*.tmp.  These seem to be created by the JDBC driver.
Steps to Reproduce:
Subject server to database load, then create heap dump and view objects in java.io.DeleteOnExitHook -> java.util.LinkedHashSet
Actual Result: 
Objects accumulate in java memory.
Expected Result: 
Objects do not accumulate in java memory
Any Workarounds: 
Using reflection a custom function can be written and scheduled to run to manually clean the DeleteOnExitHook queue.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID:	4073011
External Customer Info:
External Company:  
External Customer Name: Michael Littleton
External Customer Email:  
External Test Config: My Hardware and Environment details: CF 10,  Windows 2012, SQL  Server 2012, JVM1.7
  Attachments:
Comments: