You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ariel Weisberg (JIRA)" <ji...@apache.org> on 2015/11/11 21:58:11 UTC
[jira] [Comment Edited] (CASSANDRA-9085) Bind JMX to localhost
unless explicitly configured otherwise
[ https://issues.apache.org/jira/browse/CASSANDRA-9085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15001071#comment-15001071 ]
Ariel Weisberg edited comment on CASSANDRA-9085 at 11/11/15 8:57 PM:
---------------------------------------------------------------------
I've had to deal with the RMI GC issue before. There are properties you can set to have the GCs occur less often/never so you can allow explicit gc for things like DBB memory. I also think it's longer than 30 seconds by default?
This is where I last had to tackle it https://issues.voltdb.com/browse/ENG-5856
We actually don't want to enable explicit GC as it has valid uses for reclaiming direct byte buffers.
was (Author: aweisberg):
I've had to deal with the RMI GC issue before. There are properties you can set to have the GCs occur less often/never so you can allow explicit gc for things like DBB memory. I also think it's longer than 30 seconds by default?
This is where I last had to tackle it https://issues.voltdb.com/browse/ENG-5856
> Bind JMX to localhost unless explicitly configured otherwise
> ------------------------------------------------------------
>
> Key: CASSANDRA-9085
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9085
> Project: Cassandra
> Issue Type: Bug
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Priority: Critical
> Fix For: 2.0.14, 2.1.4
>
>
> Cassandra's default JMX config can lead to someone executing arbitrary code: see http://www.mail-archive.com/user@cassandra.apache.org/msg41819.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)