cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-4376) fails to run and/or log a message when JMX access files do not exist
Date Tue, 26 Jun 2012 16:04:53 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-4376.
---------------------------------------

    Resolution: Not A Problem

the output log is stdout/stderr from before log4j is initialized, and/or libraries that don't
use log4j
                
> fails to run and/or log a message when JMX access files do not exist
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-4376
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4376
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.1
>            Reporter: Marcos Dione
>            Priority: Minor
>
> You can specify in the cassandra-evn.sh file the settings for JMX access such as:
> JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.access.file=/etc/cassandra/jmx_acc"
> JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.password.file=/etc/cassandra/jmx_pwd"
> If any of those files doesn't exist, cassandra fails to run (most possibly a good course
of action) but doesn't log anything in the system.log, leaving the admin wondering what's
wrong.

--
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

        

Mime
View raw message