On 4 August 2017 at 09:18, Antonio Gomes Rodrigues <[email protected]> wrote: > Hi all, > > By default in "JDBC Connection Configuration", the value of "Max Number of > Connections" is 10 > > If we check the documentation we have: > > Maximum number of connections allowed in the pool. In most cases, set this > to zero (0). This means that each thread will get its own pool with a > single connection in it, i.e. the connections are not shared between > threads. If you really want to use shared pooling (why?), then set the max > count to the same as the number of threads to ensure threads don't wait on > each other. > > In particularity "If you really want to use shared pooling (*why?*)" > > Why not to set the value to 0 by default?
Discrepancies such as this are generally caused by wishing to remain compatible. The default for new test plans could perhaps be set to 0 along with changing the docs. But it's vital that existing test plans are not affected. > Cdlt, > Antonio
