You're on the right track, a Connection Pool is the correct answer to your
question.  But the servlet or tomcat (just like most things in computer
science) doesn't do anything you don't tell it to do.  You'll have to either
use a Connection Pool from your JDBC driver (if it supports that) or add one
of your own.
  (*Chris*)

----- Original Message -----
From: "Fawaz Ahmad" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 25, 2002 8:52 AM
Subject: [SERVLET-INTEREST] DB Connection and Servlets


> Hello,
>
> I was reading a post from yesterday about having multiple connections to a
> servlet with one database connection.  What is the best "professional" way
> to achieve this?  If I am using a servlet over cgi in order to save the
> overhead of connecting to a database each time, and am creating the
> connection to the database in the init() will the servlet or tomcat
> automatically create a pool of connections if i am expecting multiple
> access to the servlet at once?
>
> Also, I know this is OT, but has anyone had problems using functions other
> than next() with the Microsoft JDBC Driver for SQL Server 2000 from the MS
> website?  It won't allow functionality for previous(), etc.
>
> Thanks,
>
> Fuz
>
>
___________________________________________________________________________
> 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
>
>

___________________________________________________________________________
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

Reply via email to