Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v5.10.x] [mysql] Identity datasource pool options are not generated properly #219

Open
chalitha1989 opened this issue May 14, 2020 · 3 comments
Assignees
Labels
Milestone

Comments

@chalitha1989
Copy link

Description:

According to IS config generation values (repository/resources/conf/default.json), it only populates shared db 's pool params by default but not the identityDb params.

"database.shared_db.id": "SHARED_DB",
"database.shared_db.pool_options.maxActive": "50",
"database.shared_db.pool_options.maxWait": "60000",
"database.shared_db.pool_options.testOnBorrow": "true",
"database.shared_db.pool_options.validationInterval": "30000",
"database.shared_db.pool_options.defaultAutoCommit": "true",
"database.shared_db.jmx_enable": "false",

As a result, the datasource will be configured only with the validation query ('SELECT 1'). We need to fix this in [1]

[1]

[database.identity_db.pool_options]

Suggested Labels:
5.10.0

Suggested Assignees:
NA

Affected Product Version:
5.10.0

OS, DB, other environment details and versions:
mysql

Steps to reproduce:

Related Issues:
NA

@chirangaalwis chirangaalwis added this to the 5.10.0.2 milestone May 20, 2020
@chirangaalwis chirangaalwis changed the title [5.10.0] [mysql] Identity datasource pool options are not generated properly [v5.10.x] [mysql] Identity datasource pool options are not generated properly May 20, 2020
@chirangaalwis
Copy link
Member

chirangaalwis commented Aug 5, 2020

@omindu shouldn't we address this within the product and add the relevant default values in the default.json (at least from future versions)?

Also, can we depend on the relevant DB pool options and their mapping default values which had been used in past IS versions for version 5.10.0, as well (since, for this product version we may have to explicitly define them in customized deployment.toml file within the installation resources)?

@chirangaalwis
Copy link
Member

chirangaalwis commented Aug 6, 2020

As per internal discussion with @omindu, it was suggested that this will be fixed at the product level in future releases (see wso2/product-is#9155).

@chirangaalwis
Copy link
Member

Moving to Future milestone as this will be handled in the product in future releases.

@chirangaalwis chirangaalwis modified the milestones: 5.10.0.2, Future Aug 7, 2020
@omindu omindu removed their assignment Apr 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants