-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
PLEASE read the question!!!
50 processes IS NOT 50 connections.
You can run up 50 processes easily inside of 2 connections. They are not
the same thing.
Sure too many connections will eat up processes, but 50 processes <> 50
connections!!!!!!!!!!!!!!!!
Thor HW
----- Original Message -----
From: James Cooper <[EMAIL PROTECTED]>
To: Java Apache Users <[EMAIL PROTECTED]>
Sent: Thursday, August 12, 1999 11:34 AM
Subject: Re: keeping a handle on JDBC connections
> -----------------------------
> Please read the FAQ!
> <http://java.apache.org/faq/>
> -----------------------------
>
>
>
> On Thu, 12 Aug 1999, jon * wrote:
>
> > the beauty is that you can get a connection from anywhere in your code
> > without having to pass a connection object around or store the
connection
> > cache in your servlet.
>
> I agree.
>
> The only reason I could see for having multiple pools is if you are
> logging into a unique database, or with a unique username, per servlet.
>
> 50 connections seems like a bunch.. in my experience a pool of say 15
> connections can service 80-100 HTTP requests/second, since each thread
> only needs the connection for the duration of their sql transaction (say,
> 100-200ms).
>
> but every application is different, has different needs, etc.
>
> cheers
>
> -- James
>
>
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/main/mail.html>
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
