ReadyAPI VirtServer: baixar versions anteriors

Features and improvements
- ReadyAPI version 4.2.0 compatibility: Updated for compatibility with ReadyAPI 4.2.0. For version pairings, see ReadyAPI-VirtServer Compatibility Matrix.
- Built-in OpenTelemetryTM observability: Monitor virtual service performance in real time by pushing metrics to any OTel-compatible backend, including Prometheus and Grafana. For configuration details, see Configure Observability.
- High-throughput and stability improvements: VirtServer 3.34.0 delivers faster, more reliable request handling under load. Response-time consistency also improves, particularly for high-throughput deployments with large payloads.
Note
The Congestion behavior setting is no longer functional. Use soapui.virt.request.suspendMultiplier to control the maximum request queue size instead. For details, see Thread management JVM options.
- Thread management improvements: VirtServer reworks thread management for faster error handling and more efficient thread use. Two new VMOptions, soapui.virt.request.suspendTimeout and soapui.virt.request.suspendMultiplier, give you control over request queuing behavior. SmartBear recommends scaling the maximum number of threads to twice the number of processors. For configuration details, see JVM Settings.
- Data Encryption Standard (DES) decryption removed: VirtServer 3.34.0 has removed the legacy DES encryption mechanism to align with ReadyAPI 4.2.0 and current security standards. If you work with projects created in ReadyAPI versions earlier than 3.57.0, see the ReadyAPI 4.2.0 release notes before upgrading.
- Docker Hub documentation updated: The VirtServer Docker image documentation on Docker Hub has been updated with revised prerequisites, new image tags, and refreshed configuration examples.
Bug fixes
- Fixed an issue that prevented Secure Sockets Layer (SSL) from working when configured for a service in ReadyAPI and then deployed to VirtServer.

- Support for ReadyAPI version 4.1.0: VirtServer is recommended for use with ReadyAPI 4.1.0. For version pairings, see ReadyAPI-VirtServer Compatibility Matrix.
- Endpoint-level latency control: VirtServer now supports endpoint-level latency control, configured through REST and SOAP Virtual Services in ReadyAPI.
- HAR logging stability during performance tests: Fixed an issue where HAR logging stopped working during performance tests. HAR logs now reliably capture request and response data throughout the test run.

- High-Traffic Response Processing Improvements: Improved request processing for large virtual services under high-traffic conditions. Previously, delayed response writing could cause gateway timeouts and HTTP 500 responses when concurrent requests saturated ForkJoinPool (FJP) threads. VirtServer now uses refactored parallel request processing to reduce thread bottlenecks and head-of-line blocking during concurrent request handling. This improvement is available in ReadyAPI 3.67.0 when used with VirtServer 3.32.0.
- OpenAPI 3.1 Response Handling Improvements: Improved support for OpenAPI 3.1 virtual services to align response behavior with OpenAPI 3.0. VirtServer now correctly resolves values in OAS 3.1 structures, preventing empty responses in certain scenarios.
- Set-Cookie Header Handling Fix: Resolved an issue that prevented transaction logs from displaying when virtual service responses included a Set-Cookie header. VirtServer now also handles invalid or incomplete Set-Cookie values without throwing exceptions.
- Special Character Handling in Virtual Service Names: Resolved an issue that caused errors when virtual service names contained special characters such as :, ?, or spaces. VirtServer now sanitizes unsupported filename characters before constructing Windows file paths.

- Support for ReadyAPI version 3.65.0: Updated VirtServer to support ReadyAPI version 3.65.0, including type casting in Conditional Match responses. VirtServer 3.31.0 works best with ReadyAPI 3.65.0. For recommended VirtServer and ReadyAPI version pairings, see ReadyAPI-VirtServer Compatibility Matrix.
- Spring Framework Annotation Resolution Improvement: Improved annotation detection in Spring Framework scenarios involving parameterized supertypes with unbounded generics. Previously, annotations on methods in generic superclasses or interfaces might not resolve correctly, which could affect authorization decisions when using Spring Security’s @EnableMethodSecurity. This improvement ensures consistent behavior for applications that rely on method-level security in these hierarchies.
- Java 21 LTS: Updated the supported Java runtime to Java 21 LTS.
- Parallel Request Handling (RIA-25726): Fixed an issue that caused HTTP 500 errors when performance tests sent two or more parallel requests to a ReadyAPI/VirtServer virtual service. Sequential requests worked correctly, but parallel requests triggered an ArrayIndexOutOfBoundsException in the REST dispatch layer. This issue no longer occurs.
- Java Runtime Requirement: VirtServer has been upgraded to Java 21 LTS. As of VirtServer CLI version 3.31, Java 21 LTS is the minimum required runtime to run the CLI JAR.

- Support for ReadyAPI version 3.63.0: Updated VirtServer to support ReadyAPI version 3.63.0, including Conditional Match with query parameters and path variables.
- Spring Framework Enhancement: Updated the annotation detection mechanism to improve framework efficiency and reliability.

- Support for ReadyAPI version 3.62.0: Updated VirtServer to support ReadyAPI version 3.62.0.
- File-Based Licensing Support Removed: As outlined in our File-based License End-of-Support Policy, support for Protection LS and file-based license types has been removed from ReadyAPI. The licensing code has been refactored. Only SLM licenses are now supported.
- Accessibility Improvements: Introduced several accessibility improvements as part of an ongoing effort to comply with Web Content Accessibility Guidelines (WCAG).
- Bug Fix: Resolved an issue in SwaggerHub where mocks created from API definitions with nested references did not return the correct response. Mocks now return the expected response with the specified body in the API.

- Support for ReadyAPI version 3.61.0: Updated VirtServer to support ReadyAPI version 3.61.0, including support for OpenAPI Specification (OAS) 3.1 and Jakarta-based JMS implementations. This includes compatibility with WebLogic 12 and 14.
- Preservation of User Modifications: VirtServer Now preserves user-added modifications during upgrades, reducing post-upgrade effort. For more details, see the Custom JVM Options section and the Custom certificate configuration section.
- Performance Optimizations: Applied performance optimizations to VirtServer’s default configuration to improve startup time and runtime efficiency.
- Accessibility Improvements: Continued enhancements to VirtServer UI accessibility, improving compliance with accessibility standards and overall usability.

- Support for ReadyAPI 3.59.0 and Partial OAS 3.1 Compatibility: VirtServer now supports ReadyAPI 3.59.0 projects, including partial support for OAS 3.1. Future updates to both ReadyAPI and VirtServer will further enhance OAS 3.1 compatibility.
- End of Support for Maven Plugin: Maven plugin version 1.0.9 remains fully compatible with VirtServer 3.25.0 and aims to maintain compatibility with later releases. However, we no longer provide support for the Maven plugin and will not address any issues in future updates.
- Improved Handling of Boolean and Numeric Values in Conditional Match: In ReadyAPI 3.59.0, we've introduced an option to automatically detect boolean and numeric values in Conditional Match responses and remove quotes around them. VirtServer now supports this feature. For more details, refer to the VirtServer Configuration table on the VirtServer Settings File page.

- Enhanced Compatibility with ReadyAPI: VirtServer 3.25.0 now supports ReadyAPI 3.58.0.
- Additional Configuration Required for Route to Live:
When using Route to Live for Virtual Services deployed to VirtServer, ensure the appropriate vmoptions are configured in the following scenarios:
- To allow restricted headers.
- If the backend server uses a self-signed certificate.
- If a proxy is enabled.
For detailed instructions on adding vmoptions, refer to this page.
- Improved CLI Login Messaging: The CLI now provides clearer error messages when incorrect values are entered in the login command and OIDC is not enabled.
- Excel Data Source Issue Resolved: We fixed an issue where the Excel Data Source did not work when generating responses for virtual services in VirtServer, despite working in ReadyAPI.
- Route to Live Feature Fixed: We addressed an issue where the Route to Live feature did not function correctly in VirtServer. If no response is received from the live endpoint, the default response is now sent as expected.
- Proxy Configuration Bug Fixed: VirtServer no longer displays an error when the proxy configuration mode is set to "none" or left empty during startup. It now starts without issues.
- Optimized Garbage Collection: We addressed an issue that led to increased garbage collection in VirtServer, enhancing overall performance and efficiency.