cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Alves (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4615) cannot set log4j level on modules/classes
Date Tue, 04 Sep 2012 22:05:07 GMT


David Alves commented on CASSANDRA-4615:

The way it is setup right now, in order for tracing appender to be used in debug level, the
root logger was set to DEBUG and the other appenders were set to INFO. This unfortunately
has the side effect of not being able to lower only a particular logger to debug (because
the root is already at debug).

The other strategy would be to have an alternative logger for tracing, but this cannot be
done at the conf file level only, the actual instance of Logger would have to be a different
one. I mean instead of Logger logger = LoggerFactory.getLogger(CassandraServer.class); we
would have to use a particular one, like Logger logger = LoggerFactory.getLogger("tracing-logger");.

I chose the first one because it didn't mean changing code (just the conf file).
> cannot set log4j level on modules/classes
> -----------------------------------------
>                 Key: CASSANDRA-4615
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Brandon Williams
>            Assignee: David Alves
>            Priority: Minor
> For example, setting 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:

View raw message