cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6404) Tools emit ERRORs and WARNINGs about missing javaagent
Date Sun, 09 Feb 2014 14:28:19 GMT


Brandon Williams commented on CASSANDRA-6404:

You probably aren't running quite what you think you're running, it should be easy to tell
if you look at the shell script though.  That said, as the description says, this is harmless.

> Tools emit ERRORs and WARNINGs about missing javaagent 
> -------------------------------------------------------
>                 Key: CASSANDRA-6404
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>             Fix For: 1.2.14, 2.0.4
>         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
>  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 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

View raw message