[
https://issues.apache.org/jira/browse/CASSANDRA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092954#comment-13092954
]
Hudson commented on CASSANDRA-2857:
-----------------------------------
Integrated in Cassandra-0.8 #298 (See
[https://builds.apache.org/job/Cassandra-0.8/298/])
fix log4j initialization in EmbeddedCassandraService
patch by jbellis; reviewed by tjake for CASSANDRA-2857
jbellis :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1162851
Files :
* /cassandra/branches/cassandra-0.8/CHANGES.txt
*
/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/service/AbstractCassandraDaemon.java
*
/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/thrift/CassandraDaemon.java
> initialize log4j correctly in EmbeddedCassandraService
> ------------------------------------------------------
>
> Key: CASSANDRA-2857
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2857
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Trivial
> Fix For: 0.8.5
>
> Attachments: 2857-drivers.txt, 2857.txt
>
>
> Currently, ECS.cleanUpOldStuff calls CleanupHelper.cleanupAndLeaveDirs(),
> which initialized DatabaseDescriptor which does some logging. When we go to
> initialize log4j later in AbstractCassandraService, it's too late.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
