Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-user@jakarta.apache.org
Message-ID: <20010921161518.5703.qmail@web9607.mail.yahoo.com>
Date: Fri, 21 Sep 2001 17:15:18 +0100 (BST)
From: "=?iso-8859-1?q?C.=20Schlegelmilch?=" <c_schlegelmilch@yahoo.com>
Subject: Re: JDBC Connection Pool Theory ??
To: tomcat-user@jakarta.apache.org
In-Reply-To: <CAEAIPODDHFOIGHELHEDGEBBDKAA.jshoberg@cbd.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

We had our web development class develop their own
software for connection pooling.  These are extremely
simple soluitons but they work quite well for the
small to medium traffic they are likely to get.  

They are using "Professional Java Server Programming"
as a reference and it has some interesting sections on
Connection Pooling.  This is good if you're only
running a simple application.  It was also noted that
this resource did not address any synchronization
issues which is very important (the last thing you
want is two seperate threads getting a reference to
the next free connection at the same time).  This is
really the only big gottcha that we found in a simple
implementation.

 --- Jon Shoberg <jshoberg@cbd.net> wrote: > 
> 	Can anyone suggest or point to readings on JDBC
> connection pool theory?
> Something that covers how a pool is implemented,
> best case / worst case
> scenarios, tips and traps.
> 
> 	My next web application is looking to be very
> database (mysql) intensive.
> I would like a pooling mechanism that is VERY simple
> to use, VERY light, low
> overhead, and portable.  Having looked at packages
> such as poolman, I
> decided I need to learn a bit more about JDBC and
> pooling in general.  Any
> thoughts ?
> 
> Jon
>  

____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie