Scylla JMX proxy
Go to file
Amnon Heiman 649922fed8 Updating the http client and support API exception
The API returns errors with an HTTP code 400, 404 or 500 depending on
the cause with a json object that contains the failure reason.  The
error message should be populate to the JMX calling client, translated
to the appropriate exception.

This patch adds the ability to detect API failure and throw a runtime
exception with the returned message.

It is up to the calling method what to do with the exception, if it
would do nothing, the calling client would get a RuntimeException,
depends on origin MBean definition, the caller can catch the exception
and throw a specific kind.

Note that any exception that is thrown must be known to the JMX client
or it will not be able to process it.

As a first step, this patch replaces the jersey client to the newer
version under glassfish, which has an easy way of getting a Reply
object, and check its status before returning the results.

The only difference in the method that uses the APIClient is the use of
MultivaluedHashMap.

The following MBean implementation where changed

ColumnFamily
CompactionManager
Gossiper
EndpointSnitchInfo
CacheService
StorageProxy
StorageService

Signed-off-by: Amnon Heiman <amnon@scylladb.com>
2015-10-28 11:25:37 +02:00
debian dist: add debian/ directory to build .dep package for Ubuntu 2015-10-27 04:17:13 +09:00
dist dist: add build script for ubuntu 2015-10-27 04:17:13 +09:00
scripts JMX run scripts: Set the rmi port to listen on the jmx port 2015-09-22 10:19:53 +03:00
src/main/java Updating the http client and support API exception 2015-10-28 11:25:37 +02:00
LICENSE.AGPL Change license to AGPLv3 2015-09-22 13:33:24 +03:00
NOTICE Add a NOTICE file for the yammer library 2015-06-11 14:32:45 +03:00
pom.xml Updating the http client and support API exception 2015-10-28 11:25:37 +02:00
README.md README: Use of uber-jar and open jmx 2015-09-18 07:50:09 +03:00
SCYLLA-VERSION-GEN release: prepare for next version cycle 2015-09-21 16:17:32 -07:00

Urchin JMX Interface

This is the JMX interface for urchin.

Compile

To compile do:

mvn install

Run

The maven will create an uber-jar with all dependency under the target directory. You should run it with the remote jmx enable so the nodetool will be able to connect to it.

java -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=7199 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -jar target/urchin-mbean-1.0.jar

Setting IP and Port

By default the the JMX would connect to a node on the localhost on port 10000.

The jmx API uses the system properties to set the IP address and Port. To change the ip address use the apiaddress property (e.g. -Dapiaddress=1.1.1.1) To change the port use the apiport (e.g. -Dapiport=10001)