shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Les Hazlewood (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SHIRO-428) AuthorizingRealm "no cache" logging should be at DEBUG level, not INFO, OR is should log only once
Date Sat, 11 May 2013 22:53:16 GMT

     [ https://issues.apache.org/jira/browse/SHIRO-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Les Hazlewood updated SHIRO-428:
--------------------------------

    Fix Version/s:     (was: 1.2.2)
                   1.3.0
                   1.2.3
    
> AuthorizingRealm "no cache" logging should be at DEBUG level, not INFO, OR is should
log only once
> --------------------------------------------------------------------------------------------------
>
>                 Key: SHIRO-428
>                 URL: https://issues.apache.org/jira/browse/SHIRO-428
>             Project: Shiro
>          Issue Type: Improvement
>          Components: Authorization (access control) 
>    Affects Versions: 1.2.1
>            Reporter: Raman Gupta
>            Priority: Trivial
>             Fix For: 1.2.3, 1.3.0
>
>
> The org.apache.shiro.realm.AuthorizingRealm contains the following:
> log.info("No cache or cacheManager properties have been set.  Authorization cache cannot
" +
>     "be obtained.");
> When running without a cache manager, this spams the log files when running at INFO level.
This should either:
> 1) Be logged at DEBUG level, or
> 2) Be logged only once at INFO level.

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