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] [Updated] (DERBY-5937) File handle is leaked when a Slave replication is shutdown with failover=true
Date Tue, 16 Oct 2012 19:35:05 GMT

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

Knut Anders Hatlen updated DERBY-5937:
--------------------------------------

    Attachment: backport-10.8.diff

In addition to the issues seen when backporting to 10.9, the test framework on the 10.8 branch
is missing functionality for adding permissions incrementally, so I had to disable the security
manager in the test case in order to get it to compile on 10.8. See the attached backport-10.8.diff
patch.

All the regression tests ran cleanly on the 10.8 branch.
                
> File handle is leaked when a Slave replication is shutdown with failover=true
> -----------------------------------------------------------------------------
>
>                 Key: DERBY-5937
>                 URL: https://issues.apache.org/jira/browse/DERBY-5937
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.8.2.2
>         Environment: Windows 7
>            Reporter: Glenn McGregor
>            Assignee: Knut Anders Hatlen
>              Labels: derby_triage10_10
>             Fix For: 10.9.1.1, 10.10.0.0
>
>         Attachments: backport-10.8.diff, backport-10.9.diff, d5937-1a-test.diff, d5937-2a-close.diff,
d5937-3a-test-datasource.diff
>
>
> As part of our use of derby replication, we shut the slave down if we detect reachability
issues with the master. Normally we shut it down, and bring it back up as a regular database
in read-only mode.  Then when the master can, it tries to push a fresh copy back to the slave
system. However, during the failover=true shutdown on the slave, the log file  ".../name/log/log1.dat"
is still open. 
> Because of this open file, at least on Windows, it's impossible to move the database
file out of the way, and to install a fresh copy from the master.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message