Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <16261061.1174595852791.JavaMail.jira@brutus>
Date: Thu, 22 Mar 2007 13:37:32 -0700 (PDT)
From: "A B (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-2456) File stream is left open when an
 exception occurs while setting up a character stream for data export.
In-Reply-To: <29020342.1173985149272.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

A B resolved DERBY-2456.
------------------------

    Resolution: Fixed

Than you for addressing this so quickly, Suresh!  I'm resolving and closing the issue after confirming that the re-enabled JUnit fixture is now running without problems.

If I'm closing this prematurely, feel free to re-open it--but since it looks like you've solved the problem I was seeing, I think its safe to close this one out?

Thanks again!

> File stream is left open when an exception occurs while setting up a character stream for data export.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2456
>                 URL: https://issues.apache.org/jira/browse/DERBY-2456
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 10.3.0.0
>            Reporter: A B
>         Assigned To: Suresh Thalamati
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>
> The JUnit test tools/ImportExportTest.java has been failing since it was first contributed with the following error:
> ImportExportTest:embeddedjunit.framework.AssertionFailedError: extinout\T1.dat
> at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDir(DropDatabaseSetup.java:102)
> at org.apache.derbyTesting.junit.DropDatabaseSetup.access$000(DropDatabaseSetup.java:38)
> at org.apache.derbyTesting.junit.DropDatabaseSetup$1.run(DropDatabaseSetup.java:77)
> at java.security.AccessController.doPrivileged1(Native Method)
> at java.security.AccessController.doPrivileged(AccessController.java:287)
> at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDirectory(DropDatabaseSetup.java:74)
> at org.apache.derbyTesting.junit.SupportFilesSetup.tearDown(SupportFilesSetup.java:107)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> Also fails with the client, as well. 
> Per the comment posted by Suresh to DERBY-2295, it looks like the cause of this failure is that  the "openFile()" method of java/engine/org/apache/derby/impl/load/ExportWriteData.java does not close the file stream in cases where an invalid encoding is specified.

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