[
https://issues.apache.org/jira/browse/DERBY-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-5937:
--------------------------------------
Issue & fix info: Patch Available
All the regression tests ran cleanly on Solaris.
There were two failures on Windows. One of them looked identical to the already
known instability logged as DERBY-5866. The other failure was in
lang/triggerGeneral.sql, apparently caused by a race between the B-tree
post-commit worker thread and SYSCS_DIAG.LOCK_TABLE, resulting in more locks
than expected in the lock table. I couldn't find any JIRA issue for the latter
failure, so I'll file a new one.
None of the test failures seem to be related to the patch, so I'm setting the
Patch Available flag.
> 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
> Attachments: d5937-1a-test.diff, d5937-2a-close.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
