Gerolf Seitz 17435d6e99 Sandbox: Remove streaming connections (#3682) ... * Sandbox: Remove streaming connections The separate database connection pool for streaming connections was only used for the active contracts stream. However, a single db connection was being occupied until the last active contract was streamed over the Ledger API to the client. This effectively means that only ever 2 concurrent active contract streams could exist. No need to say that this is bad design. The following changes happened: - remove the db connection pool for streaming connections - replace the streaming mechanism for active contracts with the already existing pagination mechanism in JdbcLedgerDao - change the pagination mechanism to actually use database level limit and offset instead of doing the pagination "client side" - configure the HikariDataSource with the metric registry CHANGELOG_BEGIN - [Sandbox] Improve loading of active contracts for the Sandbox SQL backend. CHANGELOG_END * Extract PaginatingAsyncStream from JdbcLedgerDao for testing * Reset metrics registry before each test		2019-12-06 10:58:10 +00:00
..
src	Sandbox: Remove streaming connections (#3682)	2019-12-06 10:58:10 +00:00
BUILD.bazel	Add an initial version of DAML script (#3428)	2019-11-12 18:02:14 +01:00