Personally speaking, I do not run JMX on 8080, and never have. The tools, like cassandra-cli and nodetool expect it to be on the default port, but you can override with -p or -jmxport
-sd On Tue, Jun 21, 2011 at 1:33 PM, osishkin osishkin <osish...@gmail.com> wrote: > I did, and everything seemed to work fine. > But I saw a reference here > http://www.onemanclapping.org/2010/03/running-multiple-cassandra-nodes-on.html > That said "make sure you have at least one node listening on 8080 > since all the Cassandra tools assume JMX is listening there", and then > remembered that I saw a warning regarding that port when we uploaded > one of the machines. > Unfortunately I don't have access to them currently, so I can't > replicate it immediately. > > but I thought perhaps someone can repute my fear that there is > something special about that port > > On Tue, Jun 21, 2011 at 2:28 PM, Sasha Dolgy <sdo...@gmail.com> wrote: >> it's defined in $CASSANDRA_HOME/conf/cassandra-env.sh >> >> JMX_PORT= >> >> Have it different for each instance ... >> >> On Tue, Jun 21, 2011 at 1:24 PM, osishkin osishkin <osish...@gmail.com> >> wrote: >>> I want to have several deamons running on a machine, each belinging to >>> a multi-node cluster. >>> Is that a problem in concern to port 8080, for jmx monitoring? >>> Is it somewhere hardcoded, so that changing it is the configuration >>> files is not enough? >>> >>> Thank you >>> osi >> > -- Sasha Dolgy sasha.do...@gmail.com
