Skip to content

Releases: epam/Wilma

V1.1.73

11 Aug 19:51
Compare
Choose a tag to compare

With this release a new wilma-service-api library was released, and the stability and the reliability of the Wilma application was increased. See details below.

  • Internal self-defense mechanism was further enhanced (see #55)
  • wilma-service-api library become available in JCenter (see #46). This offers the possibility of using a library in you own application/component, and configure the running Wilma instance(s) from your code. For further details on the available wilma-servica-api calls, visit this page
  • A new version of browsermob-proxy-for-wilma module was released (1.1.32), and in use in this Wilma release (see #38)
  • Functional test engine was upgraded to Gepard 4.0 (see more info on Gepard here and its release on Github here)

NOTE: This release is available from Docker Hub too, see details here.

V1.1.27

10 Jun 22:03
Compare
Choose a tag to compare

With this release the stability and the reliability of the Wilma application was increased:

  • Internal self-defense mechanism was reviewed and enhanced, Wilma easily can handle high traffic for long term.
  • Extra information on problematic request/response pairs going through the Wilma proxy was added to the application log, in order to identify the captured messages.

In case you upgrade it from the previous version, it is possible to replace the jar(s) only - jars can be found in the released zip files.

V1.1.24, Java 1.8 compatible version

13 May 19:37
Compare
Choose a tag to compare

This release has no feature changes, just the libraries were upgraded and from now on both Java 1.7 and 1.8 can be used.
In case of 1.8, the memory usage is a bit more aggressive than in case of 1.7, so it is suggested to monitor the heap usage and allocate the appropriate heap size accordingly.

In case you upgrade from the previous version, it is possible just replace the jar(s), but be aware, that a new property is added to wilma.conf.properties, and without it, Wilma cannot start:

# The maximum value of displayed messages.
message.log.UI.maxsize=500

This new property controls the length of the message list presented on Wilma / Message Logs UI, to avoid listing several thousand messages when Wilma deals with high traffic.

V1.0.17, First OS release

09 Mar 16:17
Compare
Choose a tag to compare

This is the first open-sourced release of Wilma V1.0.
Feel free to use it.

See complete documentation about the product here: http://epam.github.io/Wilma/