Warn: TarMK filer reaper Unable to remove file ... The process cannot access the file because it is being used by another process.

[bobbym33667819]

Hi,

I'm getting the following warning constantly since today:

30.03.2018 09:59:28.226 *WARN* [TarMK filer reaper [F:\aem6.3\author\crx-quickstart\opt\helpers\..\..\repository\segmentstore]] org.apache.jackrabbit.oak.segment.file.FileReaper Unable to remove file F:\aem6.3\author\crx-quickstart\opt\helpers\..\..\repository\segmentstore\data00016a.tar

java.nio.file.FileSystemException: F:\aem6.3\author\crx-quickstart\opt\helpers\..\..\repository\segmentstore\data00016a.tar: The process cannot access the file because it is being used by another process.

at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)

at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)

at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)

at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)

at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)

at java.nio.file.Files.deleteIfExists(Unknown Source)

at org.apache.jackrabbit.oak.segment.file.FileReaper.reap(FileReaper.java:73)

at org.apache.jackrabbit.oak.segment.file.FileStore$3.run(FileStore.java:245)

at org.apache.jackrabbit.oak.segment.file.SafeRunnable.run(SafeRunnable.java:67)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.runAndReset(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

I'm checking those files in in Windows resource monitor but no other process seems to be using them. The warning is thrown for multiple .tar files.

Any ideas or suggestions will be greatly appreciated.

Thank you,

Bobby

[wasil_z · Accepted solution]

Use -Dsun.arch.data.model=32 as JVM argument. See related thread [1].

Thanks

Wasil

[1] AEM 6.3 offline Tar compaction error under Windows

[bobbym33667819]

Thanks,

Is that the same as setting tarmk.mode = 32 in org.apache.jackrabbit.oak.segment.SegmentNodeStoreService since I'm using the online compaction in 6.3? After I did tarmk.mode = 32 and ran the Revision Clean Up task I now have only one .tar file that can not be removed instead of several.

Thanks,

Bobby

[wasil_z]

Yes.

[sarikajain]

Is having one Tar file issue with AEM performance? I want to know what impact do having one tar file has?

[wasil_z]

Please elaborate your question.

Thanks,

Wasil