All Versions
10
Latest Version
Avg Release Cycle
132 days
Latest Release
3105 days ago
Changelog History
Changelog History
-
v2.0.0-M3
July 18, 2016 -
v1.6.2 Changes
June 20, 2019- ➕ Add support to load multiple CA certs from store
-
v1.6.1 Changes
May 01, 2019- ➕ Add configuration option authMatch which explains how to combine multiple authenticators if MultiAuthenticator is used.
- ➕ Add BigInteger simplifier. BigInteger becomes a JSON object with the key "bigint" containing the big integer value as String.
- ➕ Add configuration option threadNamePrefix which will be used by jolokia http server executor. Default: "jolokia-"
- When strict-checking is enabled for a CORS policy, then reject a request also when no Origin or Referer header is given.
-
v1.6.0 Changes
June 25, 2018- 0️⃣ Enable authentication with role "jolokia" for the war agent by default.
- ➕ Add new "jolokia-unsecured.war" which unsecured as "jolokia.war" in version 1.5.0 and below.
-
v1.5.0 Changes
February 08, 2018- Restrict allowed mime types to
text/plain
andapplication/json
for the response. - 🔒 Because of security reasion, the JSR-160 proxy mode is disabled by default int the Java EE agent. It can be enabled via
web.xml
configuration, a system property or an environment variable. In addition it is now possible to configure a whitelist with patterns which are allowed as targets in the proxy mode. See the reference manual section on "Proxy mode" for details. - 🆕 New authMode
service-any
andservice-all
to allow to lookup anorg.jolokia.osgi.security.Authenticator
used for authentication. Note that this class has been changed from an abstract base class to an interface for ease of customization.
- Restrict allowed mime types to
-
v1.4.0 Changes
January 23, 2018- ✂ Removed ChunkedWriter to avoid references and inclusion of parts of StreamEncoder which is a Java internal class
- 🛠 Fix incorrect CORS header
- 👌 Support "max connection per route" setting for J4pClientBuilder to prevent a ConnectionPoolTimeoutException
- ⚡️ Update to httpcore 4.4.7 for the Java client
- ➕ Add debian package generation to the JVM agent
- 🔧 Print all configuration value for the
/version
command: When not set explicitly then print the default value (if any). - Modifications to make JVM Agent work on IBM JVM 8.
-
v1.3.7 Changes
July 06, 2017- 👌 Support attaching to running JVM even when -XX:+PerfDisableSharedMem is given
- 👍 Better error message for Java client
-
v1.3.6 Changes
April 03, 2017 -
v1.3.5 Changes
October 04, 2016- 👌 Support JSON streaming also for AgentServlet (WAR and OSGi agent)
- Avoid NPE in Websphere detector
- Re-add hooks for creating custom restrictors
- ➕ Added better version detection of Payara Server
-
v1.3.4 Changes
July 31, 2016- ➕ Add a quite and java.util.logging LogHandler implementations which can be used with 'logHandlerClass'
- 👍 Allow a basic auth as alternative to client cert authentication when both
--user
and--useSslClientAuthentication
is used. - 👍 Allow user-specifiable SSL / TLS protocols and ciphers to the JVM agent
- 0️⃣ JSON response is streamed by default for the JVM agent to reduce memory activity
- ➕ Add the possibility to add a SSL connection factory the J4pClient
- 🛠 Fixed TomcatDetector to match more flexibly
- ✂ Removed Java 1.7 exception class, make the agent working with Java 1.6 again.