Java Possible FileChannel.map Bug

Question

So I'm trying to read in a very large file using a mapped FileChannel.

The file exceeds 2GB. A snippet of code is:

long fileSize = 0x8FFFFFFFL;
FileChannel fc = new RandomAccessFile("blah.huge", "rw").getChannel();
fc.map(FileChannel.MapMode.READ_WRITE, 0, fileSize);

This throws an error:

Exception in thread "main" java.lang.IllegalArgumentException: Size exceeds Integer.MAX_VALUE
   at sun.nio.ch.FileChannelImpl.map(FileChannelImpl.java:789)

FileChannel.map takes a long as the file size. So does this error make sense? Why would they not provide support for bigger files than that?

Working as documented, downvote.

user207421
– user207421

2011-09-24 01:41:59 +00:00
Commented Sep 24, 2011 at 1:41 — user207421
– user207421, Commented Sep 24, 2011 at 1:41
+1: Documenting a limit exists doesn't mean it makes sense.

Peter Lawrey
– Peter Lawrey

2011-09-24 07:01:45 +00:00
Commented Sep 24, 2011 at 7:01 — Peter Lawrey
– Peter Lawrey, Commented Sep 24, 2011 at 7:01

Peter Lawrey · Accepted Answer · 2011-09-24 06:59:24Z

4

The native methods this function uses does take long values without reporting an error. You can call them using reflection. However you would have test whether they work for you on your system and using memory mapping this way, could confuse you more than be useful.

The best approach is to create an array of MappedByteBuffers, e.g. 1 GB each in size and create a wrapper which hides this ugliness.

While not technically a bug, it is BAD (Broken As Designed) Part of the reason this was done originally could be that 32-bit JVM could not support this, but I don't see why 64-bit JVMs still have this limit.

answered Sep 24, 2011 at 6:59

Peter Lawrey

535k83 gold badges770 silver badges1.2k bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Hugh · Accepted Answer · 2011-09-24 01:20:40Z

2

This is not a bug. FileChannel#map is documented as requiring a size argument not greater than Integer.MAX_VALUE, which makes sense as e.g. ByteBuffer#get takes an integer for its index parameter.

answered Sep 24, 2011 at 1:20

Hugh

8,9422 gold badges39 silver badges43 bronze badges

2 Comments

poy Over a year ago

Interesting... Why does the map function take a long for the size then?

Hugh Over a year ago

I would assume that it's either for homogeneity with the other FileChannel methods or in anticipation of a non-stupid ByteBuffer; I've been unable to find a justification though, and would be very interested to hear one.

Collectives™ on Stack Overflow

Java Possible FileChannel.map Bug

2 Answers 2

Comments

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related