I have increased the Max. Number of Connections from 10 to 200 now. I did this gradually test after test. But as I increase the No. of connections the throughput/sec in my Summary Report seems to be coming down. Shouldn't I see a increase in throughput as I increase the Number of Connections? And can you please let me what "Idle Cleanup Interval" field stands for. I ahve the default as 60000ms, do I have reduce this as well? My Database is configured to have 500 sessions and I want to try and use all of those 500 sessions, but seeing a decrease in Throughput as I keep increasing the number of connections doesn't make me happy. Please clarify.
Thanks. sebb-2 wrote: > > There is a pool timeout; default 10 seconds. > > I think that means that the connection pool will only give up if it > has to wait longer to get a free connection. > > So long as enough connections are returned to the pool in time, you > won't necessarily need as many as 1 per thread. But of course some > threads may wait to get a connection. > > Try increasing the connection count. > > S. > On 05/12/06, socio_pal <[EMAIL PROTECTED]> wrote: >> >> In the JDBC Connection Configuration, the Max. number of Connections as >> 10 >> and am using 50 threads to run my performance test. But my Database >> allows >> upto 500 sessions. Is there any max. limit for Jmeter? I thought 10 is >> the >> allowed number of connections, can I configure it to have more >> connections? >> But why is that I get the error only after an hour or so? I use 50 >> threads >> and ramp up period of 5 secs. So, once all the 50 threads are started >> shoudln't i get the error? My test runs successfully for an hour or so >> and >> then I get this error. Please explain as early as possible. >> >> Thanks >> >> >> sebb-2 wrote: >> > >> > The log message suggests that you have run out of connections. >> > >> > How many did you confgure? And how many threads are you running? >> > >> > >> > On 05/12/06, socio_pal <[EMAIL PROTECTED]> wrote: >> >> >> >> Hi: >> >> I get the following Error while running the Database Performance test >> >> scripts. And the error % is really high because of this issue. Please >> do >> >> explain why this is happening and how it can be fixed. I don't get >> this >> >> error when I run the test with 1 thread, but as I keep increasing the >> >> number >> >> of threads my errors occur earlier in the test. Please explain as >> early >> >> as >> >> possible why this is happening: >> >> >> >> And in my Jmeter "View Results Tree" I get the message >> >> >> "org.apache.avalon.excalibur.datasource.NoAvailableConnectionException: >> >> Could not create enough Components to service your request (Timed >> out)." >> >> under the sample Result. >> >> >> >> In the Jmeter.log file I get the following exception: >> >> >> >> JDBC Users 1-409 started >> >> 2006/11/27 13:14:44 INFO - jmeter.threads.JMeterThread: Thread JDBC >> >> Users >> >> 1-410 started >> >> 2006/11/27 13:14:44 WARN - >> >> jmeter.protocol.jdbc.config.DataSourceElement: >> >> Could not return Connection java.lang.Exception: Could not create >> enough >> >> Components to service your request (Timed out). >> >> at >> >> >> org.apache.avalon.excalibur.pool.ResourceLimitingPool.get(ResourceLimitingPool.java:350) >> >> at >> >> >> org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.get(ValidatedResourceLimitingPool.java:130) >> >> at >> >> >> org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource.getConnection(ResourceLimitingJdbcDataSource.java:222) >> >> at >> >> >> org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.sample(JDBCSampler.java:90) >> >> at >> >> org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:247) >> >> at java.lang.Thread.run(Thread.java:595) >> >> >> >> 2006/11/27 13:14:44 ERROR - jmeter.protocol.jdbc.sampler.JDBCSampler: >> >> Error >> >> in JDBC sampling >> >> org.apache.avalon.excalibur.datasource.NoAvailableConnectionException: >> >> Could >> >> not create enough Components to service your request (Timed out). >> >> >> >> >> >> Thanks >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Exceptions-during-the-DB-Performance-Test-tf2762930.html#a7703468 >> >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Exceptions-during-the-DB-Performance-Test-tf2762930.html#a7705621 >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Exceptions-during-the-DB-Performance-Test-tf2762930.html#a7707023 Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
