[
https://issues.apache.org/jira/browse/CASSANDRA-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055800#comment-13055800
]
David Allsopp commented on CASSANDRA-2383:
------------------------------------------
http://www.vipan.com/htdocs/log4jhelp.html has the following:
log4j.configuration=app_config.properties:
First call to Category.getRoot() or Category.getInstance(...) method makes
Log4j go through an initialization process. (You can watch that happening by
setting "log4j.debug=true".)
During this process, Log4j looks in the application's classpath for a
"log4j.properties" file *or the properties file you specify* via the this
property key.
However, you need to set this as a system property, for example by running your
program with java -Dlog4j.configuration=app_config.properties .... This is
because, if you set it in the configuration file, it is too late. Log4j would
have already started to read the log4j.properties file by default, if available!
> cassandra.bat does not handle folder names with space characters on windows
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-2383
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2383
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 0.7.4
> Environment: OS : windows
> java : 1.6.0.23
> Reporter: david lee
> Assignee: Benjamin Coverston
> Priority: Minor
> Fix For: 0.7.7
>
>
> when cassandra home folder is placed inside a folder which has space
> characters in its name,
> log4j settings are not properly loaded and warning messages are shown.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
