You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by Antonio Gomes Rodrigues <ra...@gmail.com> on 2017/08/04 08:18:08 UTC

Change default value for "Max Number of Connections" in "JDBC Connection Configuration"

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?

Cdlt,
Antonio

Re: Change default value for "Max Number of Connections" in "JDBC Connection Configuration"

Posted by Antonio Gomes Rodrigues <ra...@gmail.com>.
Hi,

I have made test and it's ok with Max Number of Connections to 0 by default

I have commit the change

Antonio

2017-08-04 17:09 GMT+02:00 Antonio Gomes Rodrigues <ra...@gmail.com>:

> Hi sebb,
>
> Thanks to your feedback
>
> For the moment I have only set 'Max Number of Connections' to 0 into 'JDBC
> Connection Configuration' for the 'JDBC Load Test template'
>
> I will study to change the default value in 'JDBC Connection
> Configuration' later
>
> Antonio
>
> 2017-08-04 12:39 GMT+02:00 sebb <se...@gmail.com>:
>
>> On 4 August 2017 at 09:18, Antonio Gomes Rodrigues <ra...@gmail.com>
>> 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
>>
>
>

Re: Change default value for "Max Number of Connections" in "JDBC Connection Configuration"

Posted by Antonio Gomes Rodrigues <ra...@gmail.com>.
Hi sebb,

Thanks to your feedback

For the moment I have only set 'Max Number of Connections' to 0 into 'JDBC
Connection Configuration' for the 'JDBC Load Test template'

I will study to change the default value in 'JDBC Connection Configuration'
later

Antonio

2017-08-04 12:39 GMT+02:00 sebb <se...@gmail.com>:

> On 4 August 2017 at 09:18, Antonio Gomes Rodrigues <ra...@gmail.com>
> 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
>

Re: Change default value for "Max Number of Connections" in "JDBC Connection Configuration"

Posted by sebb <se...@gmail.com>.
On 4 August 2017 at 09:18, Antonio Gomes Rodrigues <ra...@gmail.com> 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