[
https://issues.apache.org/jira/browse/DERBY-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109156#comment-13109156
]
Dag H. Wanvik commented on DERBY-5418:
--------------------------------------
Backported to the 10.8 branch as svn 1173450, closing.
> 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
> Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0,
> 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0,
> 10.5.3.0, 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Fix For: 10.8.2.2, 10.9.0.0
>
> 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
