You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2011/07/19 15:35:58 UTC

[jira] [Created] (SLING-2149) NPE in SlingLoggerConfig if log file can't be created

NPE in SlingLoggerConfig if log file can't be created
-----------------------------------------------------

                 Key: SLING-2149
                 URL: https://issues.apache.org/jira/browse/SLING-2149
             Project: Sling
          Issue Type: Bug
          Components: Commons
    Affects Versions: Commons Log 2.1.0
            Reporter: Carsten Ziegeler


If e.g. the default log writer file can't be created (e.g. the user has no permissions), then the writer with a null file handle is used nevertheless which then causes the Sling logger to end in NPEs when trying to write to the log.
If the file can't be created maybe stderr/stdout should be used

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (SLING-2149) NPE in SlingLoggerConfig if log file can't be created

Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Boston reassigned SLING-2149:
---------------------------------

    Assignee: Ian Boston
    
> NPE in SlingLoggerConfig if log file can't be created
> -----------------------------------------------------
>
>                 Key: SLING-2149
>                 URL: https://issues.apache.org/jira/browse/SLING-2149
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: Commons Log 2.1.0
>            Reporter: Carsten Ziegeler
>            Assignee: Ian Boston
>
> If e.g. the default log writer file can't be created (e.g. the user has no permissions), then the writer with a null file handle is used nevertheless which then causes the Sling logger to end in NPEs when trying to write to the log.
> If the file can't be created maybe stderr/stdout should be used

--
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

[jira] [Resolved] (SLING-2149) NPE in SlingLoggerConfig if log file can't be created

Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Boston resolved SLING-2149.
-------------------------------

       Resolution: Fixed
    Fix Version/s: Commons Log 3.0.2

fixed in r1402370. Falls back to stdout on FileNotFound or security exceptions, and uses stdout.
Added tests. I hope (think), I got the right place.
                
> NPE in SlingLoggerConfig if log file can't be created
> -----------------------------------------------------
>
>                 Key: SLING-2149
>                 URL: https://issues.apache.org/jira/browse/SLING-2149
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: Commons Log 2.1.0
>            Reporter: Carsten Ziegeler
>            Assignee: Ian Boston
>             Fix For: Commons Log 3.0.2
>
>
> If e.g. the default log writer file can't be created (e.g. the user has no permissions), then the writer with a null file handle is used nevertheless which then causes the Sling logger to end in NPEs when trying to write to the log.
> If the file can't be created maybe stderr/stdout should be used

--
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