[
https://issues.apache.org/jira/browse/DERBY-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883597#action_12883597
]
Lily Wei commented on DERBY-4717:
---------------------------------
Thanks, Kristian and Dag. The test passed for me on Windows. Yeah!!!
> Driver trace file isn't closed/released on physical connection close when
> specified with the traceFile attribute/setter
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4717
> URL: https://issues.apache.org/jira/browse/DERBY-4717
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.7.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments: derby-4717-1a.diff, derby-4717-1b.diff, derby.log
>
>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
