[
https://issues.apache.org/jira/browse/CASSANDRA-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams resolved CASSANDRA-6404.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.14
2.0.4
Reproduced In: 2.0.3, 1.2.12 (was: 1.2.12, 2.0.3)
I was going to say we can just ignore the warning via log4j-tools.conf, but
thinking it through I think it makes sense to use jamm when possible with a lot
of these. Committed, thanks.
> 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
> Assignee: Sam Tunnicliffe
> Priority: Minor
> Fix For: 2.0.4, 1.2.14
>
> 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.4#6159)
