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 "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2011/09/17 01:41:09 UTC
[jira] [Assigned] (DERBY-5418) Network server session's close
method neglects to close down any open trace file
[ https://issues.apache.org/jira/browse/DERBY-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik reassigned DERBY-5418:
------------------------------------
Assignee: Dag H. Wanvik
> Network server session's close method neglects to close down any open trace file
> --------------------------------------------------------------------------------
>
> Key: DERBY-5418
> URL: https://issues.apache.org/jira/browse/DERBY-5418
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Attachments: derby-5418.diff
>
>
> When shutting down a network server with open sessions and tracing is enabled, this can lead to file handles remaining indefinitely open (till OS process dies). When the server instance shuts down, it calls the open sessions' close method to reclaim resources. That method, unfortunately, does not shut down any open trace file.
> I saw this when debugging a test on Windows which tried to delete the trace files after shutting down the server.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira