Bug Fixes in ReadyAPI 3.40.1

Applies to ReadyAPI 3.42.1, last modified on November 28, 2022

In ReadyAPI 3.40.1, the following issues reported by our customers have been fixed:

  • Fixed a bug which was introduced in 3.40.0 where the max memory available for ReadyAPI was not computed correctly and after 10 seconds of performance tests in 3.40.0 users were getting this false error message: More than 95% of the Java heap memory is being used. The test results may be impacted. It is recommended that you increase the value of the VM option -Xmx or -XX:MaxHeapSize in the file ReadyAPI.vmoptions. Performance tests now run without any error. (RIA-19505)

  • Fixed a bug in API Discovery where filtering the results by content type did not work properly on requests with a content-type header with a different case. (RIA-19481)

  • Fixed a bug where the HTTP Monitor did not start and the error log presented a NullPointer exception. Users can now start the HTTP Monitor and visualize a list of captured requests. (RIA-19493)

  • Fixed a bug where the Authorization Scope tree under Auth Manager was not displayed in 3.40.0. This has been restored. (RIA-19510)

  • Fixed issue with Virtualisation where mocked response did not work reliably when bulk request is made. (CC-27719)

See Also

Version History
What's New in ReadyAPI

Highlight search results