Invalid argument exception when trying to seek FilePosition to LONG.MAX_VALUE

Alan Bateman Alan.Bateman at oracle.com
Thu Jun 6 14:22:12 UTC 2019



On 05/06/2019 18:06, Karan Mehta wrote:
> :
>
> Let me clarify this a bit further. If the underlying FS throws an 
> exception while seeking to LONG.MAX_VALUE, the JNI call should catch 
> it and return a No-op to the Java function, instead of throwing it 
> back further.
I don't think this make sense. The position(long) method is specified to 
throw IOException when it fails so I'm wondering what you expect the 
file position to be if it silently fails?


>
> > This is with ext4, right?  XFS is fine with it and can even write there:
>
> Can't speak for XFS, but yeah with ext4 is where I am seeing the issue.
>
Thanks Florian for the additional information on this.

-Alan.


More information about the nio-dev mailing list