You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2010/07/01 10:34:50 UTC
[jira] Closed: (DERBY-4717) Driver trace file isn't closed/released
on physical connection close when specified with the traceFile
attribute/setter
[ https://issues.apache.org/jira/browse/DERBY-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan closed DERBY-4717.
----------------------------------
Fix Version/s: 10.4.2.1
10.5.3.1
10.6.1.1
10.7.0.0
Resolution: Fixed
Thanks, Dag and Lily.
Committed and backported:
- trunk: 959550
- 10.6 : 959552
- 10.5 : 959553
- 10.4 : 959554
> 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
> Fix For: 10.4.2.1, 10.5.3.1, 10.6.1.1, 10.7.0.0
>
> 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.