SPIKE: prevent locking more than one DB connection for request

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 .

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

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.