Jolokia is a JMX-HTTP bridge giving an alternative to JSR-160 connectors. It is an agent based approach with support for many platforms. In addition to basic JMX operations it enhances JMX remoting with unique features like bulk requests and fine grained security policies.
This minor release adds cross-origin resource sharing (CORS) support to all Jolokia agents. Cross domain access can be easily restricted with Jolokia's security setup. The Javascript library already support CORS for most browsers out of the box, for IE8 and larger some special setup is still required. Transparent CORS client support for all browsers will be added to the Jolokia Javascript client in one of the next releases.
In addition the following new features were added:
All theses changes plus the bug fixes are listed in the change log.
Starting with this release, bug tracking and release planing switches over to Jolokia's JIRA instance, kindly donated by the fine guys from Atlassian.
Also, there has been some (minor) progress with the new kid in the Chili garden, Ají, a Javascript single-page-application with an MBeanBrowser and a Dashboard. I'm still looking for helping hands, there is quite a lot to do here ;-)
The first release of this year brings some updates and minor features:
The complete changes are listed in the change log. BTW, Jolokia is available now on Maven central, too.
This was an exciting year for Jolokia:
So what's next ? There will be a minor release 1.0.2 in the first january week containing some minor feature additions and library updates. And I'm going to start the work on a whole new Jolokia based open source web console, called Aji.
Please stay tuned and a happy new year !
A minor bug fix release, probably the last before Devoxx, brings also two new features:
Jolokia is now available also at Maven Central so adding the Consol Labs repository is not required anymore in your poms (except you want depend on Jolokia snapshots).
Happy Halloween ....
Meet us in Paradise at Devoxx 2011 ! "Jolokia - JMX on Capsaicin" will be presented on November 14th 2011 in Antwerp, Belgium. I'm really excited to have the chance to bring some chili pepper to this superb premium conference which I greatly enjoyed as visitor in the past. 30 minutes are surely not long enough for getting in every feature, so please le me know whether you have a favourite one.
The second conference where Jolokia will play its role this autumn is at the Open Source Monitoring Conference "Nagios Java monitoring with Jmx4Perl and Jolokia" in Nuremberg on November 30th 2011. It's a quite different talk with focus on Jmx4Perl, discovery of relevant monitoring metrics and it's configuration in a Nagios environment. Not much Java here, but tooling en masse. I'm really looking forward to this home play, too.
If you intend to participate in one of these conferences and would like some discussion about Jolokia, Jmx4Perl, JMX, Chili pepper growing, the world, you can contact me on various channels. Jolokia can be found at twitter at @jolokia_jmx, the forum or on IRC at the Freenode channel #jolokia. For a simple chat you can use also the new webchat on this site. I would really like to hear from you !
It's time to celebrate: After two and half years of hard work, Jmx4Perl and Jolokia have been all wrapped up for their 1.0 releases.
The last month the focus was on hardening this first official release. This effort is backed up by these numbers:
The detailed code metrics can be examined on Jolokia's Sonar Dashboard and it's evolution over time is documented in the time machine
I'm very confident that this 1.0.0 version is rock solid and production ready.
There has been a minor protocol change for the way how Jolokia does URL escaping for slashes within GET requests, though. This scheme is not backwards compatible to the pre-1.0 protocol (which used a different, more complicated algorithm). Clients need to be updated, which has been already done for Jmx4Perl 1.00 and of course Jolokia 1.0.0's Javascript und Java client libraries. Since Jolokia is out of beta now such kind of change won't happen in this ad-hoc manner in the future, promised.
All changes for this release are summarized as always in the change log.