cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Loy (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-2611) static block in AbstractCassandraDaemon makes it difficult to change log4j behavoiur
Date Thu, 05 May 2011 17:46:03 GMT
static block in AbstractCassandraDaemon makes it difficult to change log4j behavoiur
------------------------------------------------------------------------------------

                 Key: CASSANDRA-2611
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2611
             Project: Cassandra
          Issue Type: Improvement
          Components: Core
    Affects Versions: 0.7.5, 0.7.4
         Environment: Windows 7
            Reporter: Paul Loy
            Priority: Minor


We embed Cassandra in our application - mainly because our webservices are such a thin layer
on top of Cassandra that it really does not make sense for us to have Cassandra in an external
JVM. In 0.7.0 this was all fine. Now upgrading to 0.7.5, there is a static block in AbstractCassandraDaemon.
This gets called when the class is loaded causing us issues as we have not generated the log4j.properties
file at this point in time.

Can this not be a protected method that is called when AbstractCassandraDaemon is constructed?
That way a) I can control the behaviour and b) my log4j.properties file will have been generated
by then.

Thanks.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message