Troubleshooting SmartBear ReadyAPI Connectivity Issues on VMware Servers
Hi member, I'm currently working with SmartBear ReadyAPI hosted on VMware servers and have encountered some connectivity issues between ReadyAPI and other services. Despite following the standard setup procedures, I'm facing intermittent connectivity problems that are impacting our testing processes. Here are a few specific issues I've noticed: Inconsistent Network Connectivity: Occasionally, ReadyAPI fails to establish a connection with external services. Latency Problems: There seems to be a noticeable delay when ReadyAPI tries to communicate with other components. Error Logs: The logs show connection timeouts and errors that I’m struggling to interpret and address. I’m looking for insights or solutions on how to troubleshoot these connectivity issues effectively. Has anyone experienced similar problems? What steps or tools have you used to diagnose and resolve these issues? Any advice on optimizing VMware servers settings or configuration adjustments that could help with this situation would be greatly appreciated. Thank you in advance for your assistance! Best regards, Alisa Aine
How can I resolve storage-related performance issues with Smart Bear ReadyAPI?
Hi everyone, I’m currently experiencing some performance issues with ReadyAPI that seem to be related to storage. The performance of my test executions and data handling has been less than optimal, and I suspect it may be tied to how storage is managed or configured. How can I resolve storage-related performance issues with ReadyAPI? I’m looking for advice on diagnosing and fixing these issues, particularly in terms of optimizing storage solutions to improve ReadyAPI’s performance. Any tips or recommendations for enhancing storage efficiency and speed in this context would be greatly appreciated! Thanks for your help! Best, Jonathan Jone
Bug: : Resource from resource path is getting cleared
Hi all, I have found one bug in new Ready API version 3.54.0: Resource from resource path is getting cleared with below steps: 1) Configure and send a API request. 2) Move the cursor to resource. 3) Now again try to send the request. 4) We can see resource is now empty/cleared.
ReadyAPI OAuth 2.0 authentication
Hi, I have recently started using ReadyAPI, mainly for security tests. Our API uses OAuth, but the custom OAuth settings in Ready API does not work for us, as SSO authentication request should be a json request as below: { "client_id":"<client_id>", "client_secret":"<client_secret>" } If I hard coded the bearer token in the API header, it expires after 30 minutes while scan is still running.