Open fearmadara opened 2 weeks ago
Hi @fearmadara,
Could you please add the complete stack trace to see the root cause of the exception?
HI @KavithaSiva ,
We see that now the issue is not appearing, hence not able to get the trace, also we have noticed that this issue occurs randomly and then disappears.
Will provide the logs when it occurs again.
Thank You Regards Akash
DestinationNotFoundException: Destination could not be found for path destination-configuration/v1/destinations/OPS_OA_AUTOPI.
Hi @KavithaSiva ,
i have pasted the trace , could you please check on the issue
Thank You Regards Akash
Hi @fearmadara,
In the stack trace you included, I can see Destination could not be found for path destination-configuration/v1/destinations/OPS_OA_AUTOPI
which indicates that the destination service responded with a 404
when queried for this particular destination. Is querying for the destination working when you use a REST client like for e.g. Postman?
Where have you created the destination OPS_OA_AUTOPI? Is it in the provider or any other subscriber sub-account?
Try to print the output of AuthTokenAccessor.getCurrentToken().getJwt().getToken()
just before you call your getDestination
method.
It could be that the destination is being queried in the wrong sub-account because of a different auth token.
Regards, Kavitha
"Caused by: com.sap.cloud.sdk.cloudplatform.resilience.ResilienceRuntimeException: java.util.concurrent.TimeoutException: TimeLimiter 'class com.sap.cloud.sdk.cloudplatform.connectivity.DestinationServicesingleDestResilience' recorded a timeout exception."
Hi @KavithaSiva ,
I have pasted the new log trace, we have added the destination, and it is in a subaccount.
Hi @fearmadara,
I can see a java.util.concurrent.TimeoutException: TimeLimiter 'class com.sap.cloud.sdk.cloudplatform.connectivity.DestinationServicesingleDestResilience' recorded a timeout exception."
in your stack trace. This means that while querying the destination service the response took longer than 6 seconds(which is the default timeout value for destination retrievals).
I am not sure why the destination service takes so long to respond in your case. Can you maybe try out querying the destination service directly using a REST client like for e.g. Postman? And see if it takes long to respond?
As a side note you could also try tweaking the default timelimiter value for destination retrievals. Ensure that you use the linked code snippet once during application startup and all your subsequent calls to destination service should have an increased timeout value.
Issue Description
Important information:
Impact / Priority
Our E2E test are failing, and we notice that the issue is coming in our dev space and not in prod space
Affected development phase: Development
Impact: Impaired
Timeline: e.g. Go-Live is in 12 weeks.
Error Message
Project Details
com.sap.cloud.sdk.cloudplatform.connectivity 5.10.0
Checklist