You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Deepa Raja <De...@leeds.orange.co.uk> on 2003/04/23 17:08:43 UTC

Concurrent request and connection pooling

Hi all,

I have a problem with tomcat and connection pooling.

I was doing a load test to look at ways of improving perfomance with our application.

The  application env is

oracle 8i back end
tomcat 4.1.16
JDBC connection pooling
Red Hat Linux 
HTTP coyote Connector on port 8080.


In my case the jsp requests are generated by URL connection form a java process.
The process is actually a thread.

When I have one thread it calls a jsp waits for its response and when completed sends the next request.

In this case the JSP is not spawning any connection. It uses the connection pooling efficiently.

But when I run my application as multithreaded 
Each thread tries to call the same JSP concurrently.
In this case the JSP spawns connections to the database and the preformance has gone down.

Do any have encountered problems with concurrent request with tomcat and connection pooling?

Can some one throw some light on this one or can share their personal exprience?

Thanks in advance
Deepa





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