cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3992) Add setloglevel command to Cli to call setLog4jLevel JMX method
Date Sat, 03 Mar 2012 16:55:57 GMT

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

Brandon Williams commented on CASSANDRA-3992:
---------------------------------------------

I can see how this would seem handy for development, but really it's less powerful than changing
log4j-server.properties since it's all or nothing - you can't set a specific class/package
to DEBUG, for instance.  I haven't tested this in a while, but if you edit the log4j file
Cassandra should re-read it after a few seconds and enact the changes.
                
> Add setloglevel command to Cli to call setLog4jLevel JMX method
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-3992
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3992
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 1.0.0
>            Reporter: Maki Watanabe
>            Priority: Minor
>         Attachments: 0001-Add-setloglevel-command.patch
>
>
> Add setloglevel command to Cli which call setLog4jLevel method.
> Syntax:
>   setloglevel class level
> Supported levels are TRACE, DEBUG, INFO, WARN, ERROR.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message