Register or Login to Your Account
In JDBC adapter ,Actually we are using min pool size '0',when will use min pool size '1'.
Never ever set min pool to non zero,it will lead to stale connection
But some times i use to notice min pool size set to '1'.will you explain when will use?
By default min pool s set to 1 many people don consider n leave it as 1
Min pool is initialized when d connection is enabled
If u set to 5 then 5 connection will be initialized n available for ever these will never be used by adapter service and it will not be valid connection as we'll
for perfomance based we are using the min pool size 1....if we kept 5 also there is no problem.......but in production in some cases we have to face the issues......(for perfomance based we are using default value.....)
Nelsiri if u set pool size 5 , that means whenever the adapter service which used the connector is enabled, 5 connection pool gets allocated for the 1st time. And due to any issue occurred inside the transaction boundary ,one of the connection is not able to release itself, it will go into a deadlock situation and since min pool you have set as 5, the IS can not even release the allocated pool and from the next run of the transaction boundary there will be 5-1=4 pool size will be allocated and 1 connection will remain deadlocked forever. This effects performance. So in Production env its mandatory you must not configure min pool more that 0.
If you set min connection as '1' then it will result to stale. For best practice you can mention pool size > '1' And if you create a connection with pool size 5 which means that there is one connection which have 5 instances . And all the 5 instances shares the same connection configuration and parameters
Improve d performance by any other way than setting min pool to non zero - period
@ Piapavola Few points for accuracy
1) Connection pooling is an optional field while configuring the adapter connection and not a default one.
2) Connection pool is different than a connection; Connection pool is an array of connections which shar
I would still recommend not to set min pool > '0'. increase the expiration time if the frequency of call to DB is more, if the connection is not used at least it will expire- even for high volume projects no harm in creating the connections newly and allow then to available in pool for more time( expire time) for other threads to use.