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: 10.4.1.3, 10.3.3.0
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/[EMAIL
PROTECTED],
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.
