There a multiple channels from where support for Jolokia can be obtained. Bugs are tracked via GitHub, questions should be preferably posed in the Jolokia Forum. Thanks to ConSol* we are able to provide professional support in various ways for Jolokia, too.

On the other hand, the are ways for supporting the development of Jolokia, too. You can contribute code and bug-fixes via GitHub (prefered) or with financial support (donations via Pledgie or flattring Jolokia).

Communication channels

There's a forum for Jolokia related discussions. Don't hesitate to fill it up with your questions and suggestions.
Feel free to join us on Freenode, and discuss on #jolokia about JMX and the world. You can use this web chat for a quick contact.
Bug Reports and Feature Requests
Jolokia uses GitHub for bug tracking and release management. Please fill in any issue you find or feature requests you have.


Jolokia uses GitHub as source repository and employs a Fork + Pull Model for development. The git clone URL is

We are always looking for volunteers to enhance Jolokia. If you would like start to participate, we suggest the following way:

  • Check for an open feature request you like or open bug at GitHub.
  • Fork Jolokia by visiting the project page (use "Fork" from the menu).
  • Your contribution must be donated under the Apache Public License and you should sign-off your commits that you conform to the Developer Certificate of Origin (i.e. that you have written the code on your own). To do so, add a line Signed-off-by: Your Name <> to your commit message. (git -s will do this for you). Only real names are allowed here.
  • After finishing your implementation, send a pull request.
  • After briefly reviewing the code contribution, it will integrated into the master repository.

Please note, that all the contributed code must be licensed under Apache License Version 2 and you must sign-off the contribution (see above).


We occassionally blog on about various topics (1-2 posts per month). There are interesting use cases how to setup JSR-160 connectors for JBoss and Weblogic, what is the best way for configuring Nagios with check_jmx4perl but also about things like Java Mail mysteries. If you are interested in Jolokia stuff only, subscribe to the Jolokia RSS feed. Otherwise, with this RSS Feed you get them all (and from my co-workers as well).


If you like the software and want to spread the word, we have some quite some cool T-Shirts, Baseball Caps, Coffee Mugs, ... over there in our merchandising shop.

Professional Support

Thanks to ConSol*, we are able to offer professional support and consulting. I.e. we do (and already have done for jmx4perl with quite some success):

  • Support with certain service level agreements, up to 7x24.
  • Workshops for evaluating how to best integrate Jolokia (and jmx4perl) in your server landscape. We are especially experts for large scale integration in huge Nagios and OP5 setups, not only for monitoring JMX MBeans but for Nagios in general.
  • Consulting and custom programming, e.g. an agent manager for mass deployment of the agents to hundreds of servers.

Please contact me (either per mail at or via our contact form) if you are interested in a concrete offering or for a reference.

So, that was it for the plug ;-)

Your Support for Jolokia

Jolokia is free software, released under the business friendly Apache License. That's mostly because I believe that open source software is the real driving force behind software innovation and I highly appreciate the fine pieces of open source software engineering I had the luck to use in my daily work. I love this.

Nevertheless, if you want to support the development of Jolokia (it is still a hobby project) and you like this software you can flattr it.