You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Adam Saghy (Jira)" <ji...@apache.org> on 2025/05/12 08:50:00 UTC
[jira] [Resolved] (FINERACT-2207) The custom JDBC driver parameters are overwritten during the Fineract initialization process
[ https://issues.apache.org/jira/browse/FINERACT-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Saghy resolved FINERACT-2207.
----------------------------------
Resolution: Fixed
> The custom JDBC driver parameters are overwritten during the Fineract initialization process
> --------------------------------------------------------------------------------------------
>
> Key: FINERACT-2207
> URL: https://issues.apache.org/jira/browse/FINERACT-2207
> Project: Apache Fineract
> Issue Type: Bug
> Affects Versions: 1.11.0
> Reporter: Adam Saghy
> Priority: Minor
> Fix For: 1.12.0
>
>
> When Fineract is initialized from an empty tenant-store database it uses an environment variable ({{{}FINERACT_DEFAULT_TENANTDB_CONN_PARAMS{}}}) that can be used to pass parameters to the JDBC driver. This is useful e.g. to set parameters to support fast failover with AWS' Aurora PostgreSQL database.
> This mechanism is currently broken, as the following happens:
> * {{0001_initial_schema.xml}} → creates the {{tenant_server_connections}} table
> * {{0002_initial_data.xml}} → creates the default tenant and sets the correct value in the {{schema_connection_parameters}} column
> * {{0005_jdbc_connection_string.xml}} → overwrites the {{schema_connection_parameters}} column with the static value {{serverTimezone=UTC&useLegacyDatetimeCode=false&sessionVariables=time_zone='-00:00'}}
> The expected behavior would be to have the value of {{FINERACT_DEFAULT_TENANTDB_CONN_PARAMS}} in the {{schema_connection_parameters}} column at the end of the database initialization.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)