Continuing the last story how to setup the basic monitoring cases for JBoss AS 7 with Munin, I took the next step to enhance the monitoring in Munin by reading JMX values from the server. If you have setup and configured JBoss AS 7 correctly, you can access JMX with the jconsole application; but JBoss AS 7 comes with a different JMX transport, so as the first step, make sure you start $JBOSS_HOME\/bin\/jconsole.sh<\/i>.<\/p>\n
Choose remote process and enter service:jmx:remoting-jmx:\/\/HOST:PORT<\/a>, where HOST is the hostname or IP of your server, port defaults to 9999. As username and password you need to enter the values you have configured in mgmt-users.properties<\/i>.<\/p>\n With this setup working, I had a look on the JMX plugin in Munin, and discovered it needs to be enhanced to support the different protocol JBoss has introduced for JMX. Currently it only supports the MI\/JNDI based access. Before going into details what I changed, and how you can get the changes, here is the final setup:<\/p>\n In \/etc\/munin\/plugin-conf.d\/munin-node<\/i> we will add a new chapter for JMX:<\/p>\n Make sure to replace the constants with your values. Additionally you may need to install an additional package for the java support in munin (on Fedora \/ Centos you need to yum install munin-java-plugins<\/i>).<\/p>\n In \/etc\/munin\/plugins\/<\/i> the jmx_<\/i> executable needs to be linked to a munin probe.<\/p>\n Now you can test it with munin-run jmx_Threads -d<\/i> and will see that you can’t connect to the JXM server in JBoss AS 7. As said before the munin plugin can not yet handle the jmx-remote protocol.<\/p>\n Looking add the code in the JMX plugin, it uses the given IP and port to build the URL to connect to. We need to override this with our own url, so we need to have one new parameter, which replaces the ip and port: env.url takes the full URL to the JMX port. And because the jmx-remoting protocol needs additionally libraries – this is why there is an extra startup script for jconsole in the JBoss distribution – we need a second parameter env.classpath to add JARs to the classpath.<\/p>\n I’ve forked the munin codebase to https:\/\/github.com\/kifj\/munin<\/a>, in plugins\/javalib<\/i> and plugins\/node.d.java<\/i> you’ll find the changed files. <\/p>\n As a result the jmx_<\/i> script and the munin-jmx-plugins.jar<\/i> are handling the additional parameters. You can build it yourself or download the 2 files from here: jmx_<\/a> and munin-jmx-plugins.jar<\/a>. These need to replace the original files in \/usr\/share\/munin\/plugins\/jmx_<\/i> and \/usr\/share\/java\/munin-jmx-plugins.jar<\/i>. The libraries from env.classpath need to copied or symlinked to \/usr\/share\/java<\/i> too.<\/p>\n","protected":false},"excerpt":{"rendered":" Continuing the last story how to setup the basic monitoring cases for JBoss AS 7 with Munin, I took the next step to enhance the monitoring in Munin by reading JMX values from the server. If you have setup and configured JBoss AS 7 correctly, you can access JMX with the jconsole application; but JBoss […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9,43,3],"tags":[61,17,24,25,21],"class_list":["post-160","post","type-post","status-publish","format-standard","hentry","category-java","category-jboss-as7","category-software-development","tag-java","tag-jboss-as-7","tag-jmx","tag-jmx-remote","tag-munin"],"_links":{"self":[{"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=\/wp\/v2\/posts\/160","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=160"}],"version-history":[{"count":9,"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=\/wp\/v2\/posts\/160\/revisions"}],"predecessor-version":[{"id":297,"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=\/wp\/v2\/posts\/160\/revisions\/297"}],"wp:attachment":[{"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=160"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=160"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=160"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n[jmx_*]
\nenv.ip HOST
\nenv.port PORT
\nenv.username USER
\nenv.password PASS
\n<\/code><\/p>\n
\nln -s \/usr\/share\/munin\/plugins\/jmx_ jmx_Threads
\n<\/code> <\/p>\n
\n[jmx_*]
\nenv.url service:jmx:remoting-jmx:\/\/HOST:PORT
\nenv.port PORT
\nenv.username USER
\nenv.password PASS
\nenv.classpath jboss-logging.jar:jboss-marshalling.jar:jboss-marshalling-river.jar:jboss-remoting.jar:jboss-remoting-jmx.jar:xnio-api.jar:xnio-nio.jar
\n<\/code><\/p>\n