JDBC NoAvailableConnectionException Problem

[Sonam Chauhan <so...@ce.com.au>]

Hello JMeter Users: 

 

I have a 'heavy' test that uses the 'JDBC Sampler' - it executes about
4000 JDBC requests in 600 seconds. However, it throws
NoAvailableConnectionException errors. Here is a sample log entry: 

-------------------

<sampleResult timeStamp="1189567551455" dataType="" threadName="Surge
Test Thread Group 2-2041" label="Insert a pick ticket ..." time="10001"
responseMessage="org.apache.avalon.excalibur.datasource.NoAvailableConne
ctionException: Could not create enough Components to service your
request (Timed out)." responseCode="" success="false"><assertionResult
failureMessage="Response was null" error="false"
failure="true"/></sampleResult>

-------------------

 

The top of the test plan has a 'JDBC Connection Configuration' element
with these settings. 

Max. Number of connections = 10 

Pool timeout = 10000 (I assume this caused the error abobe)

Idle Cleanup Interval (ms) = 60000

These and all the other settings for this config element are the default
values

 

Can anyone advise me how I can address this error? 

Each of my test thread 'sleeps' for about 6 minutes to allow
transactions to propagate from source to destination systems -would
impact Idle Cleanup Interval? 

Would I increase the max number of number of connections & timeout, and
decrease idle cleanup interval? 

 

Kind regards,

Sonam Chauhan

-- 

Corporate Express Australia Ltd. 

Phone: +61-2-93350725, Email: sonam.chauhan@ce.com.au

 

Re: JDBC NoAvailableConnectionException Problem

[sebb <se...@gmail.com>]

How many threads have you got?

If you want your threads to act as independent users, then you should
set the pool size to be at least as big. This should prevent the
timeouts.

Otherwise threads may have to wait for up to the Pool timeout - which
does seem to be what is happening here.

[I'm not sure that Pooling is appropriate for JMeter ... we probably
need to add an option to have per-thread connection handling, and
allow manual connect and disconnect].

As to idle cleanup interval, I assume that is how long a connection
can be idle before it is closed, and therefore affects how often the
connections have to be recycled.

If you are trying to simulate real clients, then arrange the interval
so that it corresponds with when they would reconnect.

If you are not interested in connection overhead, then set the
interval higher than the max likely idle period.

S.
On 12/09/2007, Sonam Chauhan <so...@ce.com.au> wrote:
> Hello JMeter Users:
>
>
>
> I have a 'heavy' test that uses the 'JDBC Sampler' - it executes about
> 4000 JDBC requests in 600 seconds. However, it throws
> NoAvailableConnectionException errors. Here is a sample log entry:
>
> -------------------
>
> <sampleResult timeStamp="1189567551455" dataType="" threadName="Surge
> Test Thread Group 2-2041" label="Insert a pick ticket ..." time="10001"
> responseMessage="org.apache.avalon.excalibur.datasource.NoAvailableConne
> ctionException: Could not create enough Components to service your
> request (Timed out)." responseCode="" success="false"><assertionResult
> failureMessage="Response was null" error="false"
> failure="true"/></sampleResult>
>
> -------------------
>
>
>
> The top of the test plan has a 'JDBC Connection Configuration' element
> with these settings.
>
> Max. Number of connections = 10
>
> Pool timeout = 10000 (I assume this caused the error abobe)
>
> Idle Cleanup Interval (ms) = 60000
>
> These and all the other settings for this config element are the default
> values
>
>
>
> Can anyone advise me how I can address this error?
>
> Each of my test thread 'sleeps' for about 6 minutes to allow
> transactions to propagate from source to destination systems -would
> impact Idle Cleanup Interval?
>
> Would I increase the max number of number of connections & timeout, and
> decrease idle cleanup interval?
>
>
>
> Kind regards,
>
> Sonam Chauhan
>
> --
>
> Corporate Express Australia Ltd.
>
> Phone: +61-2-93350725, Email: sonam.chauhan@ce.com.au
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org