Hello, we are using the latest build of Hibernate Search 3.0.1 with JDK 1.6.0_03.

The indexing job works fine, but when the source indexes are being replicated we get this exception (the index files are 150MB and the JVM is started with these parameters: -Xms768m -Xmx1280m which is the max memory we can allocate)

29 May 13:30:03 ERROR store.FSMasterDirectoryProvider$CopyDirectory (FSMasterDirectoryProvider.java:194) -Unable to synchronize source of C:\Projects\GPOApps\lucene\localindex\Contract
java.io.IOException: Map failed
at sun.nio.ch.FileChannelImpl.map(Unknown Source)
at sun.nio.ch.FileChannelImpl.transferFromFileChannel(Unknown Source)
at sun.nio.ch.FileChannelImpl.transferFrom(Unknown Source)
at org.hibernate.search.util.FileHelper.copyFile(FileHelper.java:71)
at org.hibernate.search.util.FileHelper.synchronize(FileHelper.java:54)
at org.hibernate.search.util.FileHelper.synchronize(FileHelper.java:42)
at org.hibernate.search.store.FSMasterDirectoryProvider$CopyDirectory.run(FSMasterDirectoryProvider.java:189)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.OutOfMemoryError: Map failed
at sun.nio.ch.FileChannelImpl.map0(Native Method)
... 10 more

Any suggestion on how to fix this?

Thanks,
-Chris

Hi,
I think this is a bug we should report in JIRA, but please have some more checks first:

are you using 32bit OS and JDK?

You could try two things:
1) allocate LESS memory to java, your Os could need some more ram for the filetransfer.
2) update your JDK, I found some rumors about a bug in JDK which should be fixed in "some newer JDK"; unfortunately my source is not very exact and I'm not sure it's the same issue, nor which version of JDK is refers to; it is definitely a 32bit JDK v.6 but don't know which versions exactly.

Hello,
any news about your issue?
I wrote your issue in JIRA :
http://opensource.atlassian.com/project ... SEARCH-205

Hi,
it should be solved in trunk.
could you please verify the fix?

kind regards