Migration to 2.x

Jolokia 2.0 should be fully backward-compatible with versions 1.x at protocol level. This means that old jolokia.js library should work with Jolokia 2 as well.

This is true also from Jolokia Java client perspective and processing of JSON messages sent over HTTP.

However there are other aspects that need to be considered when moving from Jolokia 1 to Jolokia 2.

Servlet API compatibility

org.jolokia.server.core.http.AgentServlet which is part of org.jolokia:jolokia-server-core library is now implementing Servlet API 5 from Jakarta EE 9 specification. In fact it should be compatible with any newer Jakarta EE specification (e.g., 10) and Servlet API (e.g., 6).

This concerns also the derived org.jolokia.server.core.osgi.OsgiAgentServlet from org.jolokia:jolokia-agent-osgi which now works with new OSGi CMPN Whiteboard Specification for Jakarta™ Servlet based on Jakarta EE 9+. This means that Jolokia 2.0 OSGi bundle won’t work with Karaf 4.4 which uses Jakarta EE specification based on javax packages.

Felix HTTP has PoC module based on Jetty 12 that implements two Servlet APIs (javax and jakarta) and at [current state] it should support Jolokia 2.

In Pax Web there’s work pending on Pax Web 10 which also should support old and new Servlet API packages.

Moving to JakartaEE 9+ impacted Jolokia’s WAR agents - these use https://jakarta.ee/xml/ns/jakartaee namespace in WEB-INF/web.xml and should work in these web application servers:

Of course all JakartaEE 9+ compliant servers are supported.

Javascript support

Jolokia 1.x includes org.jolokia:jolokia-client-javascript Maven module, which packages jolokia.js, jolokia-simple.js and other libraries.

In Jolokia 2, the same Maven module can be used in your Java application, but additionally, official NPM package is available. You can install it with npm i jolokia.js or yarn add jolokia.js.

There are several other Jolokia NPM packages available, so mind that jolokia.js is the official one.

The minimum supported JavaScript version is now ES5. For environments with ES3 and older JavaScript versions, keep using old versions of the JavaScript client provided with Jolokia 1.x.

Since it is based on ES5, JSON2.js is no longer required. You can also use it with a TypeScript project, as the client provides its type definitions with the package.

Reorganized modules

Jolokia 2 modules are organized into extensible core module and pluggable services. More information can be found on Libraries page.

Because important Jolokia functionality has been split across server and service modules, at least 3 modules are now needed to provide the same functionality which was provided by single org.jolokia:jolokia-core library from Jolokia 1.

These required modules are:

  • org.jolokia:jolokia-server-core provides request processing framework, extensible request handling, configuration classes and AgentServlet (among others)

  • org.jolokia:jolokia-service-serializer provides Java to JSON serialization services

  • org.jolokia:jolokia-service-jmx provides local request handler and JMX command handlers (read, exec, search, …​) to handle JMX operation on locally reachable MBeans and MBeanServers

Jolokia JVM Agent module

In order to have one size fits all solution, it’s enough to include one Jolokia dependency in your Maven project and Servlet API library of your choice (jolokia-server-core has a dependency on jakarta.servlet:jakarta-servlet-api in provided scope)

<dependency>
    <groupId>org.jolokia</groupId>
    <artifactId>jolokia-agent-jvm</artifactId>
    <version>2.0.1</version>
</dependency>

This brings in the following dependencies to your project:

+- org.jolokia:jolokia-agent-jvm:jar:2.0.1:compile
|  +- org.jolokia:jolokia-server-core:jar:2.0.1:compile
|  +- org.jolokia:jolokia-server-detector:jar:2.0.1:compile
|  +- org.jolokia:jolokia-service-serializer:jar:2.0.1:compile
|  +- org.jolokia:jolokia-service-jmx:jar:2.0.1:compile
|  +- org.jolokia:jolokia-service-discovery:jar:2.0.1:compile
|  +- org.jolokia:jolokia-service-history:jar:2.0.1:compile
|  +- org.jolokia:jolokia-service-jsr160:jar:2.0.1:compile
|  +- org.jolokia:jolokia-service-notif-pull:jar:2.0.1:compile
|  +- org.jolokia:jolokia-service-notif-sse:jar:2.0.1:compile
|  \- com.googlecode.json-simple:json-simple:jar:1.1.1:compile
+- org.jolokia:jolokia-support-jmx:jar:2.0.1:compile

Using org.jolokia:jolokia-agent-jvm dependency is a safe bet, as all required libraries (except Servlet API, which is in provided scope, so should be also provided by you) are brought in.

There’s also a second flavor of org.jolokia:jolokia-agent-jvm with javaagent classifier (which is downloaded as jolokia-agent-jvm-2.0.1-javaagent.jar file) that shouldn’t be used as normal Maven dependency. Instead this version enbeds its dependencies and provides shaded (with maven-shade-plugin) version of com.googlecode.json-simple:json-simple library. This version of JVM Agent is to be used specifically outside of Maven project - in container images or standalone applications using -javaagent:/path/to/agent.jar JVM argument.

Removed modules

  • jolokia-roo:jolokia-roo for Spring Roo is no longer available. Spring Roo was kind of experiment before highly successful Spring Boot.

  • org.jolokia:jolokia-osgi-bundle (with embedded Felix HTTP) is no longer available. Normal org.jolokia:jolokia-agent-osgi should be used with OSGi runtime supporting OSGi CMPN Whiteboard Specification for Jakarta™ Servlet

  • org.jolokia:jolokia-mule agent is no longer available, but because Jolokia 2 (and 1) simply provides servlet implementation, it can be used in any environment hosting a servlet container

Changed modules

  • org.jolokia:jolokia-spring library (org.jolokia:jolokia-support-spring in Jolokia 2) is no longer including META-INF/spring/jolokia.xml resource ready to be used with your Spring Framework XML DSL (using <import resource="classpath:META-INF/spring/jolokia.xml" />). There are other options for Spring Framework and Spring Boot integration presented in reference manual.

Configuration option changes

  • listenForHttpService option is now deprecated and registerWhiteboardServlet should be used instead in OSGi environments. The reason is that Jolokia 2 switched from OSGi CMPN Http Service to OSGi CMPN Whiteboard Specification for Jakarta™ Servlet.

  • dispatcherClasses option is removed. In Jolokia 1.x it was used to add org.jolokia.service.jsr160.Jsr160RequestHandler to a list of available request handlers. In Jolokia 2, this class is dicovered using new service extension model of Jolokia, when jolokia-service-jsr160 is available on the CLASSPATH (or in WEB-INF/lib of the WAR, which is the case for jolokia-agent-war).

  • Jolokia checks some configuration values also from system properties and environment variables. For example discoveryAgentUrl option can be specified as jolokia.discoveryAgentUrl system property or JOLOKIA_DISCOVERY_AGENT_URL environment variable. However some options had different format of related system property. In Jolokia 1.x, jsr160ProxyAllowedTargets could be specified as org.jolokia.jsr160ProxyAllowedTargets system property. Now all system properties have jolokia. prefix only.

  • allowDnsReverseLookup option defaults to false in Jolokia 2.

  • includeStackTrace option defaults to false in Jolokia 2.

Jolokia MBean changes

Jolokia 1 registers jolokia:type=Config which combines history and debug attributes and operations:

Jolokia 1 jolokia:type=Config MBean

Jolokia 2 registers jolokia:type=Config with just debug attributes and operations, while history part is contained in separate jolokia:type=History MBean.

Also agent=<agentId> key is added to all Jolokia MBean names.

Jolokia 2 MBeans

Other changes

  • For Spring support, in jolokia-config.xsd, references to SLF4J (enumerations, config options) are renamed from sl4j to slf4j. Also log4j2 enum is used instead of log4j.