[
https://issues.apache.org/jira/browse/OAK-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615491#comment-15615491
]
Tomek Rękawek commented on OAK-4274:
------------------------------------
It's also worth to note the difference between UNIXes and Windows. While UNIX
allows to remove mmapped file, Windows throws an exception saying that the
file is still in use.
For the segment-tar [we saw|OAK-4828] such exceptions on the Windows machines,
which may mean that the file has not been released (possibly because of the
buffer leakage mentioned by Michael/Francesco).
> Memory-mapped files can't be explicitly unmapped
> ------------------------------------------------
>
> Key: OAK-4274
> URL: https://issues.apache.org/jira/browse/OAK-4274
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar, segmentmk
> Reporter: Francesco Mari
> Labels: gc, resilience
> Fix For: 1.6, 1.5.14
>
>
> As described by [this JDK
> bug|http://bugs.java.com/view_bug.do?bug_id=4724038], there is no way to
> explicitly unmap memory mapped files. A memory mapped file is unmapped only
> if the corresponding {{MappedByteBuffer}} is garbage collected by the JVM.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
