Unfortunately, you can't change the interface jmx binds to initially. So in order to accomplish what you want you will need to use different jmx ports for each process.
This is how ccm (https://github.com/pcmanus/ccm) accomplishes this as well. On Wed, Feb 5, 2014 at 9:35 AM, Kyle Crumpton (kcrumpto) <kcrum...@cisco.com > wrote: > Hi Andrey, > > I only see a port for JMX. I do not see a value for the interface. I am > using Cassandra 1.2.6 > > From: Andrey Ilinykh <ailin...@gmail.com> > Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org> > Date: Tuesday, February 4, 2014 4:46 PM > To: "user@cassandra.apache.org" <user@cassandra.apache.org> > Subject: Re: Question 1: JMX binding, Question 2: Logging > > JMX stuff is in /conf/cassandra-env.sh > > > On Tue, Feb 4, 2014 at 2:25 PM, Kyle Crumpton (kcrumpto) < > kcrum...@cisco.com> wrote: > >> Hi all, >> >> I'm fairly new to Cassandra. I'm deploying it to a PaaS. One thing this >> entails is that it must be able to have more than one instance on a single >> node. I'm running into the problem that JMX binds to 0.0.0.0:7199. My >> question is this: Is there a way to configure this? I have actually found >> the post that said to change the the following >> >> JVM_OPTS="$JVM_OPTS -Djava.rmi.server.hostname=127.1.246.3" where >> 127.1.246.3 is the IP I want to bind to.. >> >> This actually did not change the JMX binding by any means for me. I saw a >> post about a "jmx listen address" in cassandra.yaml and this also did not >> work. >> Any clarity on whether this is bindable at all? Or if there are plans for >> it? >> >> Also- >> >> I have logging turned on. For some reason, though, my Cassandra is not >> actually logging as intended. My log folder is actually empty after each >> (failed) run (due to the port being taken by my other cassandra process). >> >> Here is an actual copy of my log4j-server.properites file: >> http://fpaste.org/74470/15510941/ >> >> Any idea why this might not be logging? >> >> Thank you and best regards >> >> Kyle >> > >
