[
https://issues.apache.org/jira/browse/OAK-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved OAK-1530.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.19
Assignee: Jukka Zitting
Thanks for the JVM bug link! That seems a more likely cause of this problem.
In revision 1579024 I added an workaround that explicitly catches these
exceptions and logs only a milder warning with a reference to the JVM issue.
> TarMK thread logs warning
> -------------------------
>
> Key: OAK-1530
> URL: https://issues.apache.org/jira/browse/OAK-1530
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, segmentmk
> Affects Versions: 0.18
> Environment: Windows 7, JDK 1.7.0_51 64 Bit
> Reporter: Marcel Reutegger
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 0.19
>
>
> From time to time I see warnings from the TarMK flush thread. I'm not sure if
> this is caused by my environment. In any case it would be good to at least
> know why it happens and then fix or document it.
> {noformat}
> 12.03.2014 10:54:45.752 *WARN* [TarMK flush thread: repository]
> org.apache.jackrabbit.oak.plugins.segment.file.FileStore
> Failed to flush the TarMK at repository
> java.io.IOException: The process cannot access the file because another
> process has locked a portion of the file
> at java.nio.MappedByteBuffer.force0(Native Method)
> at java.nio.MappedByteBuffer.force(MappedByteBuffer.java:203)
> at
> org.apache.jackrabbit.oak.plugins.segment.file.MappedAccess.flush(MappedAccess.java:73)
> at
> org.apache.jackrabbit.oak.plugins.segment.file.TarFile.flush(TarFile.java:181)
> at
> org.apache.jackrabbit.oak.plugins.segment.file.FileStore.flush(FileStore.java:225)
> at
> org.apache.jackrabbit.oak.plugins.segment.file.FileStore$1.run(FileStore.java:196)
> at java.lang.Thread.run(Thread.java:744)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
