Details
-
Bug
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
None
-
None
-
CP: Sprint 154, CP: Sprint 155, CP: Sprint 156
-
3
-
Core: Platform
-
Implementation coding issue
Description
.onComplete(v -> { if (v.failed()) { pgClient.rollbackTx(conn, done -> { log.error("Error in request processing", v.cause()); promise.fail(v.cause()); }); } else { context.forEach(p -> eventPublisherService .publishLogRecord(new JsonObject().put(REQUESTS.value(), p), REQUEST_EXPIRED)); pgClient.endTx(conn, done -> promise.complete()); } })));
If eventPublisherService.publishLogRecord throws an exception the promise is neither failed nor completed and the request to /scheduled-request-expiration will never get any response. /scheduled-request-expiration is called every 2 minutes. This might be the cause of OKAPI-1141.
TestRail: Results
Attachments
Issue Links
- relates to
-
CIRCSTORE-391 /scheduled-request-expiration hangs on invalid URL or unknown host
-
- Closed
-
-
CIRC-1783 Very slow check out behavior observed in Nolana Hotfix #1
-
- In Code Review
-
-
OKAPI-1141 In new/old volaris 1/2nd environment unable to create loan policies.
-
- Blocked
-