[
https://issues.apache.org/jira/browse/CASSANDRA-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133466#comment-13133466
]
David Allsopp commented on CASSANDRA-2611:
------------------------------------------
Is this now resolved? Since 0.8.5 the relevant code in AbstractCassandraDaemon
is in a static method (called by a static block in the
org.apache.cassandra.thrift.CassandraDaemon subclass). Or does that just move
the problem to the subclass if that is used in the embedded system?
> 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.4, 0.7.5
> Environment: Windows 7
> Reporter: Paul Loy
> Priority: Minor
> Labels: daemon, initialisation, log4j
>
> 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.
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
