[ 
https://issues.apache.org/jira/browse/FINERACT-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17183549#comment-17183549
 ] 

Petri Tuomola commented on FINERACT-1115:
-----------------------------------------

In FINERACT-796, Fineract was changed to use the Hikari connection pool rather 
than the Tomcat one. So the parameters passed to configure the connection pool 
in Tomcat config are no longer used - instead, the HikariCP is configured based 
on the following environment variables:

        <property name=_"driverClassName"_ value=_"${fineract_tenants_driver}"_ 
/>

        <property name=_"jdbcUrl"_ value=_"${fineract_tenants_url}"_ />

        <property name=_"username"_ value=_"${fineract_tenants_uid}"_ />

        <property name=_"password"_ value=_"${fineract_tenants_pwd}"_ />

So as far as I can see, when you update the MySQL password, you should set the 
environment variable _${fineract_tenants_pwd}_ instead.

 

> Not possible to start tomcat if root password is not "mysql"
> ------------------------------------------------------------
>
>                 Key: FINERACT-1115
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1115
>             Project: Apache Fineract
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.4.0
>            Reporter: Francis Guchie
>            Priority: Critical
>              Labels: beginner
>             Fix For: 1.0.0, 1.1.0, 1.2.0, 1.3.0
>
>
> After a successfull installation following steps here 
> [https://mifosforge.jira.com/wiki/spaces/docs/pages/74711072/Mifos+X+Installation+on+Linux+-+Ubuntu+Server]
>  , it was possible to change the suggested root password for MySQL. 
> But for the latest build, if you change the root password from "mysql" to 
> something else, when you start tomcat, you will get errors. This looks like 
> the root password (the suggested one) is hard coded in some files of the 
> fineract



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to