Configure Hikari Pool for DataServices

Data Services
1

Apparently with DS 2023-06 the properties to control the Hikari connection pool have changed.

Before that we were able to configure the pool size using:

spring.datasource.hikari.maximum-pool-size=..
spring.datasource.hikari.minimum-idle=..

However, these have no effect with 2023.06. Appending an s doesn’t help either:

spring.datasources.hikari.maximum-pool-size=..
spring.datasources.hikari.minimum-idle=..

I also tried:

spring.datasources.dataservices.hikari.maximum-pool-size=..

without success.

So how can we configure the pool size for DS in that version?

2

Hi @thomas-soft-grove
From version 36.0.0, DS team has introduced Content Store module for storing attachments and thumbnails (see GetA12 doc). It means that now there are 2 separate datasource configurations:
spring.datasources.dataservices.hikari.maximum-pool-size for dataservices core
and
spring.datasources.contentstore.hikari.maximum-pool-size for content store.
I don’t know if the content store is the case that you want to configure.

3

As I wrote, I tried that version.

My spring properties contain

spring.datasources.dataservices.hikari.maximum-pool-size=2
spring.datasources.contentstore.hikari.maximum-pool-size=2

But I still see 10 connections for dataservices and 10 for the contentstore in the database.

The value is both defined in Spring’s properties file and an Environment variable (because that’s how it’s done in production for our project)

4

Hello,
this is a known bug of DS. It should be fixed from version 36.2.x

5

Thanks.

Is there a JIRA ticket for that bug?

6

Hi,
Unfortunately, I’m not finding any ticket related, I do know a PR for that, will send you via Webex

7

this is a known bug of DS. It should be fixed from version 36.2.x

Can you say in which .ext version this was fixed?

8

Ext3 for your information