Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 5 Sep 2012 09:27:08 +1100 (NCT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <1493787230.35308.1346797628633.JavaMail.jiratomcat@arcas>
In-Reply-To: <705305251.34857.1346792647946.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (CASSANDRA-4615) cannot set log4j level on
 modules/classes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-4615:
-------------------------------------------

so...  upgrading the trace messages to debug wouldn't help us get debug from (just) gossip in the fileappender either, i take it?
                
> 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