commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (JCI-68) FilesystemAlterationMonitor NullPointerException when directory not readable
Date Mon, 19 Aug 2013 12:15:49 GMT

    [ https://issues.apache.org/jira/browse/JCI-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743761#comment-13743761
] 

Sebb edited comment on JCI-68 at 8/19/13 12:14 PM:
---------------------------------------------------

bq. We'll have to check if the FileAlterationMonitor of commons-io is also affected by this
issue.

I just checked: Commons IO always checks for null after invoking File#listFiles
                
      was (Author: sebb@apache.org):
    bq. We'll have to check if the FileAlterationMonitor of commons-io is also affected by
this issue.

No, Commons IO always checks for null after invoking File#listFiles
                  
> FilesystemAlterationMonitor NullPointerException when directory not readable
> ----------------------------------------------------------------------------
>
>                 Key: JCI-68
>                 URL: https://issues.apache.org/jira/browse/JCI-68
>             Project: Commons JCI
>          Issue Type: Bug
>          Components: fam
>    Affects Versions: 1.1
>         Environment: Linux
>            Reporter: Jan
>              Labels: fam, permissions
>             Fix For: 1.1
>
>         Attachments: FileAlteration.java
>
>
> When one of the directories monitored by the FilesystemAlterationMonitor is not readable
by the proess, the monitoring crashes with a NullPointerException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message