What you want is a static connection pool that maintains a couple of active
connections and hands them out to your app/servlet. Many have been written.
I've used this one for a while with few modifications:
http://www.webdevelopersjournal.com/columns/connection_pool.html
Lance
----- Original Message -----
From: Jaman Burton <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 28, 2000 1:06 PM
Subject: Multi-threaded application
> Hi all,
>
> I have a question about a servlet application that I am
> developing. In a multi-threaded application is it necessary to
> register the JDBC drivers before each connection is made to the
> database? Or is registering the JDBC driver once adequate enough?
>
> Currently, each time a user attempts to log into our database, the
> application registers a JDBC driver, then calls getConnection using
> said driver. I was wondering if I could just register 1 driver then
> just call getConnection using the same driver for each login attempt.
>
> I've looked but haven't really found much documentation about
> either point and my JDBC knowledge isn't very strong.
>
> Thanks,
>
> Jaman Burton
> [EMAIL PROTECTED]
> Excel Corporation
>
>
___________________________________________________________________________
> 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
