The CreatorCon Call for Content is officially open! Get started here.

Integration is falling with error The request failed: Request not sent to uri

Meenakshi Rajes
Tera Expert

‎03-24-2023 04:49 AM

Hi Team,

 

Need assistance for the integration,

 

We have updated the endpoint in the rest message HTTP METHOD, its showing the below error in the ECC Queue,

error="The request failed: Request not sent to uri= <url of instance> : java.net.SocketException: Socket is closed" probe_time="2360" result_code="900000"

 

Gone through the KB articles KB0994104 & KB0815903.

Tried by adding the property "glide.outbound.tls_sni.enabled" its not working as expected.

 

Thanks in advance!

0 Helpfuls
  • 2,123 Views
1 REPLY 1

Ratnakar7
Mega Sage

‎03-27-2023 11:22 PM

Hi @Meenakshi Rajes ,

 

The error message indicates that the request failed because the socket is closed. This could be due to a number of reasons, such as network connectivity issues or server-side problems. Here are some steps you can take to troubleshoot the issue:

  1. Check the endpoint URL: Make sure that the endpoint URL is correct and can be reached from the instance. You can try pinging the endpoint URL or using a tool like Postman to send a test request.

  2. Check the firewall settings: Make sure that the necessary ports are open and that there are no firewall rules blocking the outbound traffic from the instance.

  3. Check the network connectivity: Check if there are any network connectivity issues between the instance and the endpoint. You can try running a traceroute or ping command to see if there are any network hops that are causing delays or drops.

  4. Check the server-side logs: Check the logs of the server that is hosting the endpoint to see if there are any errors or issues that could be causing the request to fail.

  5. Check the REST message configuration: Make sure that the REST message configuration is correct and that all the required parameters are set correctly. Double-check the HTTP method, headers, and body of the message.

  6. Try disabling TLS SNI: If you have enabled the "glide.outbound.tls_sni.enabled" property, try disabling it to see if it resolves the issue. Sometimes, enabling this property can cause issues with certain endpoints.

  7. Contact the endpoint owner: If none of the above steps resolve the issue, it could be an issue with the endpoint itself. Contact the owner of the endpoint and ask them to check if there are any issues on their side.

If my response was helpful in resolving the issue, please consider accepting it as a solution by clicking on the ✅Accept solution button and giving it a thumbs up 👍. This will benefit others who may have a similar question in the future.

 

Thank you!

Ratnakar

0 Helpfuls