| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8226614 | 14 | Andrew Dinn | P3 | Resolved | Fixed | b03 |
| JDK-8228238 | 13.0.2 | Andrew Dinn | P3 | Resolved | Fixed | b01 |
| JDK-8228023 | 13.0.1 | Andrew Dinn | P3 | Resolved | Fixed | master |
The force methods defined by MappedByteBuffer have the following statement:
"If this buffer was not mapped in read/write mode (FileChannel.MapMode.READ_WRITE) then invoking this method has no effect."
This wording needs to be changed to take account of possible implementation specific map modes (seeJDK-8221397), maybe something like:
"This method has no effect for buffers mapped in read-only or private mapping modes. It may also have no effect for other implementation specific map modes."
"If this buffer was not mapped in read/write mode (FileChannel.MapMode.READ_WRITE) then invoking this method has no effect."
This wording needs to be changed to take account of possible implementation specific map modes (see
"This method has no effect for buffers mapped in read-only or private mapping modes. It may also have no effect for other implementation specific map modes."
- backported by
-
JDK-8226614 (bf) MappedByteBuffer.force method may have no effect on implementation specific map modes
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- csr for
-
JDK-8226385 (bf) MappedByteBuffer.force method may have no effect on implementation specific map modes
-
- Closed
-
- relates to
-
JDK-8221397 (fc) Support implementation-defined Map Modes
-
- Resolved
-