[DERBY-4717] Driver trace file isn't closed/released on physical connection close when specified with the traceFile attribute/setter

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.7.1.1
• Fix Version/s: 10.4.2.1, 10.5.3.1, 10.6.2.1, 10.7.1.1
• Component/s: Network Client
• Assignee: Kristian Waagan
• Reporter: Kristian Waagan
• Created: 28/Jun/10 07:48
• Updated: 29/Nov/10 14:20
• Resolved: 01/Jul/10 08:32

Description

When specifying a trace file with the traceFile connection URL attribute or with the data source setter method, the handle to the trace file isn't released when the physical connection is closed.
The problem may be specific to the implementations of ConnectionPoolDataSource and XADataSource, as using a plain data source doesn't involve reuse (i.e another mechanism may close the trace file handle).

Two potential problems caused by this bug:
o resource leak (i.e., too many file handles open)
o trace files cannot be deleted on Windows (seen for DERBY-4709)

Issue Links

• blocks: DERBY-4709 Create test that parse client trace file to detect round-trips for Derby-4653