[
https://issues.apache.org/jira/browse/DERBY-6396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807902#comment-13807902
]
Fabian Depry commented on DERBY-6396:
-------------------------------------
This happened to one of our customers; we have not been able to reproduce the
issue ourselves. But that customer mentioned that the tmp folder became
unaccessible because of networking issues; so yes, it seems there was an I/O
problem, which is one of the two conditions under which File.list() would
return null.
It all makes sense :-)
Thanks for looking into this!
> NullPointerException in DirFile
> -------------------------------
>
> Key: DERBY-6396
> URL: https://issues.apache.org/jira/browse/DERBY-6396
> Project: Derby
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 10.10.1.1
> Environment: Windows 7
> Reporter: Fabian Depry
> Assignee: Knut Anders Hatlen
> Attachments: check-null.diff
>
>
> We got a NullPointerException trying to start a Derby database in embedded
> mode; the stacktrace indicated it happened in
> org.apache.derby.impl.io.DirFile.deleteAll(); that method got called from
> org.apache.derby.impl.io.BaseStorageFactory.createTempDir().
> After investigating, it appears that the deleteAll() method calls
> "super.list()", which according to the java.io.File specifications, can
> return null. But the deleteAll() method doesn't handle that case gracefully.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
