jmesnil / jmx4r
- Source
- Commits
- Network (3)
- Issues (1)
- Downloads (6)
- Wiki (1)
- Graphs
-
Branch:
master
jmx4r /
| name | age | message | |
|---|---|---|---|
| |
.gitignore | Sat Apr 12 11:50:35 -0700 2008 | |
| |
AUTHORS.txt | Thu Feb 12 05:00:29 -0800 2009 | |
| |
LICENSE.txt | Thu Apr 10 12:17:46 -0700 2008 | |
| |
README.rdoc | Thu Oct 22 01:41:08 -0700 2009 | |
| |
Rakefile | Thu Oct 22 05:30:53 -0700 2009 | |
| |
examples/ | Mon Jun 15 04:26:56 -0700 2009 | |
| |
lib/ | Thu Oct 22 05:36:35 -0700 2009 | |
| |
test/ | Thu Oct 22 01:41:07 -0700 2009 |
README.rdoc
jmx4r is a JMX library for JRuby.
It can be used to write simple Ruby scripts running on JRuby to manage remote Java applications (e.g. JBoss, Tomcat) using JMX.
jmx4r helps to manage Java applications using JMX in a simple and powerful way:
- no need to depend on the Java interfaces of the MBean in your management code. This means less deployment issues
- Thanks to Ruby metaprogramming toolset, you can treat your MBeans as simple objects and jmx4r hides all the complexity to map them to the javax.management API for you
- you can manage your own JVM (e.g. if you’re running a Rails on JRuby application) or a remote JVM in the same way
Installation
jruby -S gem install jmx4r
Usage
# To trigger a garbage collection on a Java application: require 'rubygems' require 'jmx4r' JMX::MBean.establish_connection :host => "localhost", :port => 3000 memory = JMX::MBean.find_by_name "java.lang:type=Memory" # display verbose GC logs memory.verbose = true # trigger a Garbage Collection memory.gc # For local processes not publishing jmxrmi ports, instead: # connect to the local JConsole process JMX::MBean.establish_connection :command => /jconsole/i
Help
Source Code
git clone git://github.com/jmesnil/jmx4r.git
