You use VirtServer to run virtual services in your network. It is an addition to ReadyAPI Virtualization that is used for creating, editing, and running virtualized services.
VirtServer is tightly integrated with ReadyAPI Virtualization, allowing you to run and manage virtual services created with ReadyAPI Virtualization and hosted on VirtServer. VirtServer runs on Windows, Linux, macOS, and headless machines .
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.
