|
Mifos X class TomcatJdbcDataSourcePerTenantService
an initial connection pool was set up for each tenant request using the following settings
poolConfiguration.setInitialSize(5);
poolConfiguration.setMaxActive(5);
poolConfiguration.setMinIdle(1);
poolConfiguration.setMaxIdle(4);
poolConfiguration.setSuspectTimeout(60);
poolConfiguration.setTimeBetweenEvictionRunsMillis(30000);
poolConfiguration.setMinEvictableIdleTimeMillis(60000);
No problem when using requests inside Mifos X but there is when running pentaho reports which request their own connection separate to this pool. After a couple of runs the pentaho report will stick... it will ask for new credentials after about a minute... and an exception starting
"Connection has been abandoned" will be issued. There may also be an exception related to "no connection available"
Commenting out all the settings except for
poolConfiguration.setInitialSize(5);
(which is the current config) then no problem running pentaho reports.
However, the connections continue increasing
(seen by) select * from information_schema.processlist in mysql GUI
until mifosx is taken down. Similar thing happens when executing thru pentaho report designer (some but not all connections hang around until closing PRD).
So, what's the best settings and is there something else that needs to happen like closing connections.
Pentaho 3.9.1
mysql-connector-java-5.1.22.jar
|
