[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: JavaHL: strange/impossible IOException

From: Branko ─îibej <brane_at_wandisco.com>
Date: Thu, 27 Aug 2015 17:50:29 +0200

On 27.08.2015 17:44, Marc Strapetz wrote:
> We have just received following bug report which shows an impossible
> stack trace:
>
>> java.io.IOException: No space left on device
>> at java.io.FileOutputStream.writeBytes(Native Method)
>> at java.io.FileOutputStream.write(Unknown Source)
>> at
>> org.apache.subversion.javahl.remote.RemoteSession.nativeGetFile(Native Method)
>>
>> at
>> org.apache.subversion.javahl.remote.RemoteSession.getFile(RemoteSession.java:167)
>
> I'm considering it as "impossible", because
> RemoteSession.nativeGetFile only throws a ClientException and no
> IOException. I guess the only possible way to throw a checked
> Exception which is not declared is from native code. Now I'm wondering
> whether this might be related to the Exception wrapping/unwrapping
> problem which Bert has addressed in r1664939 (and following)? Btw,
> these kinds of stack traces have also been reported for the
> javahl-1.8-extensions branch.

If an IOException is thrown from java.io.FileOutputStream.writeBytes and
that goes through JavaHL native code, it'll be passed back to the Java
layer, yes.

Is this a problem? Do you have any concrete suggestions about how to fix it?

-- Brane
Received on 2015-08-27 17:50:36 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.