Hi Cihad, The "connections" that the tab is referring to are ManifoldCF connections, not JDBC connection pool sizes, which is something completely different.
The JDBC connector shares access to JDBC connections across a hard-wired pool. The number hardcoded is fine until you have more than 30 worker threads; beyond that, it will function as a bottleneck. We generally don't recommend having more than 30 worker threads in any case though because those threads require more memory resources and don't help performance. If you want to revise this, the approach I'd take would be to create a new PoolManager per ManifoldCF JDBC connection. The maximum size of the pool manager would be 1, and the number of connections in the pool would also be 1. The pool would be torn down whenever the ManifoldCF JDBC connection is closed. I am not sure how well this would work but it's much more in keeping with the MCF philosophy than having connector configuration parameters that affect a global pool. Karl Karl On Fri, Jun 28, 2019 at 5:11 AM Cihad Guzel <[email protected]> wrote: > Hi Karl, > > I create a new jdbc repository connection and I set "max connections "and > "Max avg fetches/min" from throttling tab on mfc-ui. Then, I reviewed > JDBCConnectionFactory.java and I have encountered some hardcoded parameters > as follow: > > cp =_pool.addAlias(poolKey, driverClassName, dburl, userName, > password, 30, 300000L) > > Max connection is set as 30. > > Are we sure that the parameters entered from the screen are used? > > Regards, > Cihad Guzel >
