On 30-May-2000 ajaikumar peddapanga wrote:
> Hi all !
> I have a quick question .
>
> I have a servlet which needs to execute some stored procedures.I am getting
> a connection to the database in the servlet init() method.
> my servlet doesnt need any transactions .My question is ....is that one
> single Connection i get in the init() method good enough for processing any
> number of Simultaneous Requests ...or Should i use Connection Pooling to
> deal with large number of simultaneous requests.??I know for every request
> the servlet Container spawns a Thread that calls the service() Method of the
> servlet .But can the same connection be used by different Threads
> Simultaneously?
Correct me if i'm wrong but connections are sequential and can only be resued
after the request is finished and the resultset closed. So if you want
to do simultanious request you need to use connection pooling and fetch a new
connection for each request. I found that connection pooling boosts up the
performance of database request anyway so in general its the way to go.
More info on connection pooling is probably in the archives of this list.
Wouter
--
Mphasis Media BV. Interactive architects
Wouter Boers <[EMAIL PROTECTED]> http://www.MphasiS.com
Phone: +31 (0)23 5573447 Fax: +31 (0)23 5655132
Wouter Boers <[EMAIL PROTECTED]> http://www.ikke.net
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
