Jolokia provides its users with a free and fresh way for accessing JMX MBeans remotely.
Jolokia is different to JSR-160 connectors in so far as it is an agent based approach which uses JSON over HTTP for its communication in a REST-stylish way.
Multiple agents are provided for different environments:
· WAR Agent for deployment as web application in a JEE Server.
· OSGi Agent for deployment in an OSGi container. This agent is packaged as a bundle and comes in two flavors (minimal, all-in-one).
· Mule Agent for usage within a Mule ESB
· JVM JDK6 Agent which can be used with any Oracle/Sun JVM, Version 6
Here are some key features of "Jolokia":
· Firewall friendly
· Polyglot
· Simple Setup
· Bulk requests
· Fine grained security
· Proxy mode
What`s New in This Release: [ read full changelog ]
· Fixed issue with overloaded methods where one variant takes no arguments. This no-arg variant can be specified with the signature "()" after the operation name.
· Added HTTPS support for the JVM-JDK6 agent. In order to switch it on, the property "protocol=https" must be set and additional the properties "keystore" and "keystorePassword" for pointing to the keystore which holds the server side certificate. Client side certificate authentication is switched off currently alway.
· Fixed date handling when an MBean exports an attribute as date. It is now returned as an ISO-8601 formatted string, when used with a path "time" the epoch milliseconds are returned. Setting of date values and using dates as arguments for JMX operations is now also supported, the value can be given either in epoch milliseconds or as an ISO-86-1 formatted string. With a path "time" a given date value can be even updated for a write operation.
· Reworked "list" handling. It`s no much faster when used with pathes since ...
