[FOLIO-1900] SPIKE: prevent locking more than one DB connection for request Created: 25/Mar/19  Updated: 03/Jun/20

Status: Open
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Jakub Skoczen Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: platform-core
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to MODCAL-40 Investigate mod-calendar module freeze Closed
relates to RMB-354 Add PostgresClient.saveBatch variant ... Closed
Sprint:
Development Team: Core: Platform

 Description   

This is an issue to propose a solution to prevent RMB modules from locking more than one DB connection from the pool for the same user request. This can lead to a deadlock situation as seen in MODCAL-40 Closed .

One proposed solution is to allow the client to re-use the connection when accessing the DB, see RMB-354 Closed .

Another solution discussed is to automatically discover when a client attempts to retrieve another connection from the pool while already having one locked. We discussed that a notion of "request context" could be useful for tracking who uses DB connections.


Generated at Thu Feb 08 23:16:43 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.