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] Created: (DERBY-3726) Don't call RAFContainer.padFile() from instances of RAFContainer4
Date Wed, 18 Jun 2008 11:18:45 GMT
Don't call RAFContainer.padFile() from instances of RAFContainer4

                 Key: DERBY-3726
                 URL: https://issues.apache.org/jira/browse/DERBY-3726
             Project: Derby
          Issue Type: Improvement
          Components: Store
    Affects Versions:,
            Reporter: Knut Anders Hatlen
            Assignee: Knut Anders Hatlen
            Priority: Minor

In this thread on derby-dev, http://mail-archives.apache.org/mod_mbox/db-derby-dev/200806.mbox/%3c48530848.3020501@sbcglobal.net%3e,
it was mentioned that RAFContainer4 calls padFile() when creating a container. Since padFile()
uses old I/O calls and the rest of RAFContainer4 uses NIO, it could possibly cause similar
issues as those seen in DERBY-3347. Although we haven't verified that this is a problem, we
should try to avoid mixing old I/O and NIO to be on the safe side.

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

View raw message