[ABTEST-305] Handle Read timed outs when calling ApiGateway Created: 16/Sep/20  Updated: 01/Oct/20  Resolved: 30/Sep/20

Status: Closed
Project: A/B Testing
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Task Priority: Neutral
Reporter: Andrei Ichimescu Assignee: Andrei Ichimescu
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: ABTEST MVP
Sprint: Add-Ons 47
Story Points: 5

 Description   

From time to time a read timeout exception is thrown when interacting with the api-gateway:
java.net.SocketTimeoutException: Read timed out.

This Exception may have a negative impact, when the operations are not executed transactionally. e.g.: When aborting a test, the test is aborted, but deleting data in the cloud might not be executed if the timeout exception is thrown.

AC:
Handle the SocketTimeoutException gracefully and ensure the operations work as expected.

 

Dev Notes:

  • Contact Maxime to log potential errors to somewhere else and be informed about them
  • Do not block the instance, async

Generated at Sun Feb 11 22:54:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.