Addendum: I just read this advise from the DBCP configuration page, and it appears to be applicable in your case. (It seems very logical to set the maxIdle to 10 or more for your test)
If maxIdle is set too low on heavily loaded systems it is possible you will see connections being closed and almost immediately new connections being opened. This is a result of the active threads momentarily closing connections faster than they are opening them, causing the number of idle connections to rise above maxIdle. The best value for maxIdle for heavily loaded system will vary but the default is a good starting point. On May 29, 2012, at 2:23 AM, Harikrishnan R wrote: > Hi, > > I am creating a standalone application, which queries(reads) the > database upon each request. I am using Jetty server for handling incoming > request. > > For each request it is creating *DataContext.createDataContext() *to > perform query . > > By using jmeter, I put 10 request per second. It is executing the select > statements one by one, then only it is responding back. > > The poolmanager is configured (min,max) as (5,50). I am sure that > webserver is reading the 10 request simultaneously. > > > Is there any way to make the database queries(read) parallel, so that It > can respond to the request as fast as possible and withstand the load. > > > I am sure that I am missing some basic things, please guide me. > > -Regards > Harikrishnan R
