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:33:09 UTC
[jira] [Created] (DERBY-5418) Network server session's close method
neglect to close down any open trace file
Network server session's close method neglect 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
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
[jira] [Resolved] (DERBY-5418) Network server session's close
method neglects to close down any open trace file
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik resolved DERBY-5418.
----------------------------------
Resolution: Fixed
Fix Version/s: 10.8.2.2
> 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
[jira] [Assigned] (DERBY-5418) Network server session's close
method neglects to close down any open trace file
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (DERBY-5418) Network server session's close method
neglects to close down any open trace file
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-5418:
---------------------------------
Summary: Network server session's close method neglects to close down any open trace file (was: Network server session's close method neglect to close down any open trace file)
> 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
>
> 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
[jira] [Commented] (DERBY-5418) Network server session's close
method neglects to close down any open trace file
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (DERBY-5418) Network server session's close
method neglects to close down any open trace file
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (DERBY-5418) Network server session's close
method neglects to close down any open trace file
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109149#comment-13109149 ]
Dag H. Wanvik commented on DERBY-5418:
--------------------------------------
Thanks, Knut. Regressions passed, committed as svn 1173446.
> 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
[jira] [Updated] (DERBY-5418) Network server session's close method
neglects to close down any open trace file
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (DERBY-5418) Network server session's close method
neglects to close down any open trace file
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-5418:
---------------------------------
Affects Version/s: 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
Fix Version/s: 10.9.0.0
> 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.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
[jira] [Closed] (DERBY-5418) Network server session's close method
neglects to close down any open trace file
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik closed DERBY-5418.
--------------------------------
> 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