Bug Fixes in ReadyAPI 3.64.0
In ReadyAPI 3.64.0, we fixed the following issues reported by our customers:
Note
RIA-5xxx1 represents the Jira ticket number. It helps you track back the bugs resolved in version 3.64.0.
Fixed:
An issue that triggered an error message during parallel processing in Virtual Services. Accessibility changes in table sorting introduced the problem. The fix removes those changes and moves that accessibility work to the restyle project. The corresponding VirtServer release that supports this fix is scheduled for late January. (RIA-26051).
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 as expected. However, parallel requests triggered an ArrayIndexOutOfBoundsException in the REST dispatch layer. This behavior no longer occurs (RIA-25726).
A regression from version 3.62.0 that stopped the keystore dropdown from working at the request level in Properties. The initSSLSocketFactory() method in httpclientSupport() returned an SSLConnectionSocketFactory instead of the previous SoapUISSLSocketFactory, which included required fields and logic. As a result of this change, the implementation no longer passed the KeyStore into the subsequent logic. Restoring the correct return type resolves the issue (RIA-26067).
An issue in ReadyAPI 3.62.0 caused ReadyAPI to fail when acquiring a floating license during startup on a fresh installation. When ReadyAPI received a response from the SLM On-Premise server (v2.5) that the JSON parser could not process, ReadyAPI logged an exception in the SLM server logs and stopped the licensing flow. ReadyAPI now handles these responses correctly and completes floating license acquisition as expected (RIA-26044).
An issue that blocked access to the Testing from Recordings (Discovering) feature by displaying an incorrect license warning. The warning appeared even for users with a valid ReadyAPI Pro license, despite the feature being included in Pro entitlements (see ReadyAPI common features). Users can now access the feature as expected (RIA-25934).
An issue in the Data Source US ZIP Code Data Generator that produced ZIP codes beginning with 0 for most generated values when using the All format type. The generator now produces varied ZIP code values as expected. The data remains randomly generated and not validated against real ZIP codes. To generate validated ZIP codes, users should supply their own data set (RIA-26182).