[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mysql-java
Subject:    Re: In-built connection pooling in the mm.mysql driver?
From:       "Mark Matthews" <mmatthew () thematthews ! org>
Date:       2002-04-16 18:24:00
[Download RAW message or body]

It doesn't make sense for the driver to implement connection pooling itself.
If you dig deep into the ConnectionPoolDataSource specification, it's not
designed to be a connection pool...It is only there so that an application
server can register to be notified of lifecycle events on the connection
(close() being called, exceptions being thrown), to mangage a pool of the
connections itself. It has to be this way so all of the fancy transaction
management/association can work.

(See
http://www-106.ibm.com/developerworks/java/library/j-jtp0410/?open&l=907,t=g
r if you want to really see the nitty-gritty details).

Your application server (whatever it is) should provide a connection pooling
mechanism that understands either javax.sql.DataSource or
javax.sql.ConnectionPoolDataSource, both of which are supported by MM.MySQL.

If your application server does not support standards-based connection
pooling, or you aren't using an application server, I suggest looking for a
javax.sql standards-based connection pool implementation, such as Tyrex
which has been mentioned on this list (http://tyrex.exolab.org/).

    -Mark (developer of MM.MySQL)
----- Original Message -----
From: "Leo Przybylski" <leop@engr.arizona.edu>
To: "Frank Daly" <fdaly@cit.ie>; <java@lists.mysql.com>
Sent: Tuesday, April 16, 2002 11:24 AM
Subject: Re: In-built connection pooling in the mm.mysql driver?


> All,
>
> I am going to rant a little.
>
> mm.mysql does not have such support, but from what I have heard on this
list
> lately, it is probably better that way. There is some added flexibility to
> the driver without having this functionality.
>
> Vender inspecific utilities like Tyrex enhance the driver's functionality.
> That's great! This means the driver is interoperable. If there were a
> PooledDataSource implementation as part of the driver, there probably be
> issues with interoperabilty.
>
> Instead of, connection pooling questions on the list, there would be
griping
> about interoperability. Personally, I would rather hear the connection
> pooling questions.
>
> You can implement any connection pool you want, and any way you want. You
> don't even have to use the PooledDataSource if you don't want to. You can
> just use a regular DataSource implementation and have it draw from a
> connection pool.
>
> Ok, done with my rant.
> -Leo
>
> On Tuesday 16 April 2002 08:59, Frank Daly wrote:
> > Hi
> >
> > Is there in-built support for connection pooling in the mm.mysql
> > driver?  If not, which connection pooling package would you recommend?
> >
> > Thanks in advance
> >
> > Frank
> >
> >
> > ---------------------------------------------------------------------
> > Please check "http://www.mysql.com/Manual_chapter/manual_toc.html"
before
> > posting. To request this thread, e-mail java-thread3609@lists.mysql.com
> >
> > To unsubscribe, send a message to the address shown in the
> > List-Unsubscribe header of this message. If you cannot see it,
> > e-mail java-unsubscribe@lists.mysql.com instead.
>
> ---------------------------------------------------------------------
> Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
> posting. To request this thread, e-mail java-thread3612@lists.mysql.com
>
> To unsubscribe, send a message to the address shown in the
> List-Unsubscribe header of this message. If you cannot see it,
> e-mail java-unsubscribe@lists.mysql.com instead.
>
>


---------------------------------------------------------------------
Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
posting. To request this thread, e-mail java-thread3618@lists.mysql.com

To unsubscribe, send a message to the address shown in the
List-Unsubscribe header of this message. If you cannot see it,
e-mail java-unsubscribe@lists.mysql.com instead.

[prev in list] [next in list] [prev in thread] [next in thread]