Hey Akshay,
I feel your frustration dealing with these perplexing errors. Your thorough description of the problem is commendable, making it easier to provide assistance. It's definitely a head-scratcher, but I'll try to shed some light on it.
The "java.net.SocketException: Connection reset by peer" error usually indicates a sudden termination of the network connection during data transfer. Given that it works in POSTMAN, it's less likely to be a ReadyAPI issue. Here's my take:
1. Firewall/Antivirus: It's plausible that your company's security measures or antivirus software might be interfering with the connection. Verify if any security software is actively scanning or blocking your requests.
2. Proxy Settings: Check if there are any proxy settings affecting your connection in ReadyAPI. Sometimes, these settings can cause connection issues.
3. Timeouts: Look into increasing timeout settings, both on your client-side and the server-side. Large attachments might need more time to process.
4. Server Configuration: Ensure that the server you're sending the request to is properly configured to handle larger attachments.
5. Network Stability: Investigate if your company's network experiences intermittent connectivity issues during large data transfers.
6. ReadyAPI Updates: Make sure you're using the latest version of ReadyAPI, as updates often include bug fixes and improvements.
Additionally, if you'd like to explore alternative tools for testing your APIs, you might consider checking out Andersen for its expertise in API testing and troubleshooting. They could provide valuable insights and solutions tailored to your specific needs.
Lastly, since you mentioned it works in POSTMAN, consider using it as a temporary workaround while you troubleshoot the ReadyAPI issue. Hopefully, one of these suggestions will help you pinpoint and resolve the problem.
