Detect underlying cause for java.io.FileNotFoundException

Question

FileNotFoundException is thrown on all sorts of occasions - not necessarily only when the file name is invalid, but also when e. g. permissions do not allow a file to be created or read:

java.io.FileNotFoundException: \\server\share\directory\test.csv (Anmeldung fehlgeschlagen: unbekannter Benutzername oder falsches Kennwort)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
    at java.io.FileWriter.<init>(FileWriter.java:73)

The above example shows a German Windows complaining about invalid username or password.

Is there a way short of parsing the exceptions message to get a little finer grained information on why exactly the exception occurred? Problem with message parsing is that in different locales the messages will vary.

score 10 · Accepted Answer · answered Nov 02 '09 at 13:05

10

Do the check for file existence/read-write permissions yourself before creating FileOutputStream.

File test_csv = new File( "\\server\share\directory\test.csv" );

if ( test_csv.exists( ) && test_csv.canWrite( ) )
{
  // Create file writer
  ...
}
else
{
  // notify user
  ...
}

Notice that sometimes you will have to check the read/write permissions on a parent of you destination file, if you need to create a new file.

File test_csv = new File( "\\server\share\directory\test.csv" );
File parent_dir = test_csv.getParentFile( )

if ( parent_dir.exists( ) && parent_dir.canWrite( ) )
{
  // Create file writer
  ...
}
else
{
  // notify user
  ...
}

answered Nov 02 '09 at 13:05

Alexander Pogrebnyak

44,836
10
105
121

D'Oh! Sometimes life can be sooo easy. Thanks for opening my eyes to the obvious. – Daniel Schneller Nov 02 '09 at 13:24
1

Be careful. There are apparently some bugs that can affect the return result of these methods. You may get invalid results if your directory is a custom or system directory or if it is on certain types of network share. – Michael Rutherfurd Nov 03 '09 at 04:39
Apparently I just got bit by http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4939819 which will tell you that the user's home directory (documents and settings...) on Windows is not writable. Workaround: Try creating a temp file in the parent folder and delete it immediately afterwards, if successful. If an IOException is thrown, you really cannot write. – Daniel Schneller Nov 04 '09 at 10:22
Is a permissions issue possible if I am running this as administrator from Intellij? – Janac Meena Dec 18 '18 at 21:28

score 2 · Answer 2 · answered Nov 02 '09 at 12:59

2

You may want to look at the properties of the file using the java.io.File object before attempting to read the file. There's a canRead method on that you can use to determine whether or not the user can read the file.

answered Nov 02 '09 at 12:59

Chris Gow

7,514
4
23
18

score 1 · Answer 3 · answered Nov 02 '09 at 12:47

1

One approach is to look at the actual type of the exception: as you can see from the docs, there are a lot of subclasses that provide finer-grained information.

However, you probably won't get far with that. As with most checked exceptions, it's usually better to log/report the exception and ask the user for choices on how to correct it.

answered Nov 02 '09 at 12:47

kdgregory

38,754
10
77
102

Problem is I get a FileNotFoundException, not a generic IOException. I'd like to present a better user message than "File Not Found" or "Generic Error", pointing the user towards the permission problem... – Daniel Schneller Nov 02 '09 at 12:53
My mistake - I read IOException. Unfortunately, Java exceptions rarely have additional information (such as a POSIX error code), and in many cases are stretched to cover conditions that have little relationship to their name (sometimes due to assignment of POSIX code to exception type, sometimes, I think, due to laziness). – kdgregory Nov 02 '09 at 13:06

Detect underlying cause for java.io.FileNotFoundException

3 Answers3