You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (JIRA)" <ji...@apache.org> on 2013/11/25 16:35:36 UTC
[jira] [Created] (CASSANDRA-6404) Tools emit ERRORs and WARNINGs
about missing javaagent
Sam Tunnicliffe created CASSANDRA-6404:
------------------------------------------
Summary: Tools emit ERRORs and WARNINGs about missing javaagent
Key: CASSANDRA-6404
URL: https://issues.apache.org/jira/browse/CASSANDRA-6404
Project: Cassandra
Issue Type: Improvement
Components: Tools
Reporter: Sam Tunnicliffe
Priority: Minor
Fix For: 2.0.3, 1.2.12
Attachments: 0001-Set-javaagent-when-running-tools-in-bin.patch
The combination of CASSANDRA-6107 & CASSANDRA-6293 has lead to a number of the tools shipped in bin/ to display the following warnings when run:
{code}
ERROR 15:21:47,337 Unable to initialize MemoryMeter (jamm not specified as javaagent). This means Cassandra will be unable to measure object sizes accurately and may consequently OOM.
WARN 15:21:47,506 MemoryMeter uninitialized (jamm not specified as java agent); KeyCache size in JVM Heap will not be calculated accurately. Usually this means cassandra-env.sh disabled jamm because you are u
{code}
Although harmless, these are a bit disconcerting. The simplest fix seems to be to set the javaagent switch as we do for the main C* launch.
--
This message was sent by Atlassian JIRA
(v6.1#6144)