[jira] [Comment Edited] (CASSANDRA-4615) cannot set log4j level on modules/classes

["David Alves (JIRA)" <ji...@apache.org>]

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

David Alves edited comment on CASSANDRA-4615 at 9/5/12 9:15 AM:
----------------------------------------------------------------

right, you need to also down the threshold for the appender you want (probably the R one in this case).

I'll try and find find a better way to do that, but without actually using a different logger for tracing (and therefore changing quite a lot of code) it will probably depend on some weird hack to the logging system.
                
      was (Author: dr-alves):
    right, you need to also up the threshold for the appender you want (probably the R one in this case).

I'll try and find find a better way to do that, but without actually using a different logger for tracing (and therefore changing quite a lot of code) it will probably depend on some weird hack to the logging system.
                  
> cannot set log4j level on modules/classes
> -----------------------------------------
>
>                 Key: CASSANDRA-4615
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4615
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Brandon Williams
>            Assignee: David Alves
>            Priority: Minor
>
> For example, setting log4j.logger.org.apache.cassandra.db=DEBUG in the config has no effect. Perhaps there is something else that needs to be set as well, but we should at least document that there.

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