db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5418) Network server session's close method neglects to close down any open trace file
Date Mon, 19 Sep 2011 13:01:09 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107790#comment-13107790
] 

Knut Anders Hatlen commented on DERBY-5418:
-------------------------------------------

The patch looks safe to me. +1 to commit.

> 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

        

Mime
View raw message