SAP Incident 309471/2025 - Requests take intermittently long time to process because of Socket Exception

[shreyamanjunath2507]

Ask the Question

Same request calls made takes more time intermittently and the calls whose response time spent is more, stacktrace shows it is because of a Socket Exception that occurs while making a call to a destination service (Kyma).

Can I know what is causing this SocketException?

Used Versions:
Java version: Java 21
SAP Cloud SDK version: 5.17.0

stacktrace.txt

[newtork]

java.net.SocketException: Connection timed out indicates that the HTTPS connection cannot be established within a timelimit.

What is the target system you are addressing?

If it is an OnPremise system behind a Cloud Connector, then I would suggest to monitor the Cloud Connector performance/load.

[shreyamanjunath2507]

The destination is a Kyma URL.

We assumed it would be token related but were not able to confirm further.

[newtork]

Given the error message and the stacktrace, I cannot infer a cause with SAP Cloud SDK. To me it looks like your target system (on kyma) does not handle TSL/SSL connections in time. This could be due to load issues or proxy/routing problems.

If this problem is reproducible reliably, then I would suggest to try and access the same kyma resource via browser or rest-client (Bruno, Postman, Insomnia, etc) at the same time the problem occurs. Maybe you'll see that the connections times out there as well.

If you are certain the problem lies within Java runtime, i.e. SAP Cloud SDK, then maybe you'll want to try-out a different HTTP client of your choice. The Destination API offers easy access to URL, proxy and header information.

[newtork]

I looked into your SNOW ticket and want to emphasize:

• The stacktrace indicates no problem with loading the destination(s). If I'm not reading it wrong, your RemoteUserFunctionExecutor runs a generic request with HttpClient on behalf of an existing (already loaded) destination.
• In case you want the long running request to be executed longer (and not be interrupted by the exception) then you can increase the timeout.
• I've read something about "a cloud connector token stored with a destination" which seems confusing to me. Maybe you want to recheck your destination settings. Because it sounds like it contradicts your statement "The destination is a Kyma URL."