db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4717) Driver trace file isn't closed/released on physical connection close when specified with the traceFile attribute/setter
Date Mon, 28 Jun 2010 20:32:50 GMT

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

Lily Wei updated DERBY-4717:

    Attachment: derby.log

Apply the patch and test it on Windows. With or without ClienBaseDataSource changes, the tests
both failed with not privilege on delete data files on assertTraceFilesExistAndCanBeDeleted

[Error/failure logged at Mon Jun 28 13:04:48 PDT 2010]
junit.framework.AssertionFailedError: Delete failed
        at junit.framework.Assert.fail(Assert.java:47)
        at junit.framework.Assert.assertTrue(Assert.java:20)
        at org.apache.derbyTesting.functionTests.tests.jdbcapi.J2EEDataSourceTest$8.run(J2EEDataSour
        at java.security.AccessController.doPrivileged(Native Method)
        at org.apache.derbyTesting.functionTests.tests.jdbcapi.J2EEDataSourceTest.assertTraceFilesEx
        at org.apache.derbyTesting.functionTests.tests.jdbcapi.J2EEDataSourceTest.testClientTraceFil
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at junit.framework.TestCase.runTest(TestCase.java:154)
        at junit.framework.TestCase.runBare(TestCase.java:127)
        at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:109)
        at junit.framework.TestResult$1.protect(TestResult.java:106)
        at junit.framework.TestResult.runProtected(TestResult.java:124)
        at junit.framework.TestResult.run(TestResult.java:109)
        at junit.framework.TestCase.run(TestCase.java:118)

> Driver trace file isn't closed/released on physical connection close when specified with
the traceFile attribute/setter
> -----------------------------------------------------------------------------------------------------------------------
>                 Key: DERBY-4717
>                 URL: https://issues.apache.org/jira/browse/DERBY-4717
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions:
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-4717-1a.diff, derby.log
> When specifying a trace file with the traceFile connection URL attribute or with the
data source setter method, the handle to the trace file isn't released when the physical connection
is closed.
> The problem may be specific to the implementations of ConnectionPoolDataSource and XADataSource,
as using a plain data source doesn't involve reuse (i.e another mechanism may close the trace
file handle).
> Two potential problems caused by this bug:
>  o resource leak  (i.e., too many file handles open)
>  o trace files cannot be deleted on Windows (seen for DERBY-4709)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message