Guys its a web applications. And connection pooling will be provided by container. I wanted to test only the time taken by query/stored procedure, not the time of spent in opening connection.
Regards, Jehanzeb Qayyum On Wed, Jun 30, 2010 at 3:19 PM, sebb <[email protected]> wrote: > On 30/06/2010, Sudip Kumar Bhattacharya <[email protected]> > wrote: > > If it is a j2ee web application, app server wud be doing the connection > pooling. > > Yes, agreed. > > > If it is a desktop app running from multiple terminals then connection > pooling won't be there across multiple users. > > Yes, agreed. > > > I hope you are testing for a web application. > > If the OP wants to emulate the behaviour of a web application, then > they need to test using the pooling code actually used by the > applicaton, not the pooling code which happens to be used by JMeter. > > Note that the JMeter pooling implementation cannot be changed (except > by rewriting the code!). > > Alternatively, work out how many independent connections are created > by the web application, and use that many JMeter threads. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
