Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 16 Sep 2011 23:41:09 +0000 (UTC)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1513616566.37125.1316216469076.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1670160928.36992.1316215989498.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5418) Network server session's close method
 neglects to close down any open trace file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dag H. Wanvik updated DERBY-5418:
---------------------------------

    Attachment: derby-5418.diff

Uploading a patch which fixes this issue. 


> 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
>         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