[DERBY-3726] Don't call RAFContainer.padFile() from instances of RAFContainer4

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.3.3.0, 10.4.1.3
• Fix Version/s: 10.4.2.0, 10.5.1.1
• Component/s: Store
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 18/Jun/08 11:17
• Updated: 04/May/09 18:22
• Resolved: 25/Jun/08 14:34

Description

In this thread on derby-dev, http://mail-archives.apache.org/mod_mbox/db-derby-dev/200806.mbox/[e-mail]%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.