1.0.3 with CORS support

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:

• AMD support for jolokia.js and jolokia-simple.js
• Time based eviction of historical values remembered on the client side, in addition to count based eviction
• New configuration option httpServiceFilter for the OSGi agent for selection of a specific HttpService to bind to.
• None-caching headers added to the response

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 ;-)

1.0.2 released

The first release of this year brings some updates and minor features:

• The Java client library supports now using a JSR-160 proxy, too. The reference manual tells you how to provide a proxy either as a default to a J4pClient or per request.
• A configuration parameter mimeType can be either used in the global configuration or as request parameter in order to explicitely set the mime type of the returned JSON answer. By default this is text/plain, but for some environments a mime type application/json might be more appropriate.
• In case of an error on the server side, the Jolokia request leading to this error is included into the response the same way as it is done for successful responses.
• The Roo plugin has been updated for Roo 1.2 and the Jolokia Javascript library has been tested with the latest jQuery version 1.7.1

The complete changes are listed in the change log. BTW, Jolokia is available now on Maven central, too.

Happy new year 2012 !

This was an exciting year for Jolokia:

• We hit 1.0.0 in October after one year of active development
• Jolokia was presented at Devoxx 2011 in the "Tools in action" track. Despite the competition on the parallel tracks was very strong and some technical issues, I think the talk went rather well (although there is of course quite some space for improvement ;-). I blogged about my experience and you can find the full talk recorded at Parleys. In order to see the full talk you either need to wait a year or buy a 79 EU subscription from Parleys for all those fantastic talks (>120) given at Devoxx this year. The slides are given below, hosted by Slideshare and the shownotes with all the links are given our blog. Devoxx was definitely my personal highlight this year and I hope to get the chance to present in Antwerp next year, too.
• I also gave a talk at the Open Source Monitoring Conference 2011 in Nuremberg, where I was the 'Java guy' this year. It was my thirds time at OSMC and it was as always a big pleasure to meet the Nagios folks and catering was phantastic, too ;-)

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 !

1.0.1 is out

A minor bug fix release, probably the last before Devoxx, brings also two new features:

• The JVM Agent can now also take a regular expression as argument for specifying a process to attach to. This pattern is matched against the process' name. Alternatively you can of course specify the process id as before.
• Collections which are not lists or maps (like Set) are serialized properly as JSON arrays.

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 ....

Jolokia and Jmx4Perl on tour

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 !

1.0.0

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:

• 216 integration tests which has been successfully run on 38 different platforms.
• a unit test coverarge of 82.7% with 404 Java and 194 Javascript unit tests.
• a technical debt of 2% (or 8 man day) as measured by Sonar
• other Sonar metrics inlcuding:
  • 100% rule compliance
  • 0% package tangle index
  • 34.1% comments and 100% documented API
  • 94.6% total quality

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.