Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Message-ID: <20030628174605.45915.qmail@web20706.mail.yahoo.com>
Date: Sat, 28 Jun 2003 10:46:05 -0700 (PDT)
From: David Graham <grahamdavid1980@yahoo.com>
Reply-To: dgraham@apache.org
Subject: Re: DBCP status?
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
In-Reply-To: <3EFD9618.70103@joedog.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

--- Tim Funk <funkman@joedog.org> wrote:
> Tomcat (5) uses BasicDataSourceFactory (but this can be overridden via a
> 
> system property).
>
jakarta-tomcat-catalina/catalina/src/share/org/apache/naming/factory/ResourceFactory.java
> 
>
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/globalresources.html
> 
> Things I'd like to see (but stayed quiet since I don't have time just
> yet to 
> make my wishes come true)
> - Better support/debugging for forcing connections closed after being
> open 
> for "too long"

This is exactly what got DBCP into trouble in the past.  I'm -1 on
providing any ability in DBCP to close lost connections.  DBCP should
provide the ability to *log* when it detects a resource leak but the
application is responsible for the health of the pool.

David


> - Code walkthrough so everything is JMX friendly, from there - that
> should 
> let me do the following:
>   -- Query all datasources (quantity)
>   -- See the following stats for each datasource
>      - Open connections
>      - Borrowed Connections
>      - High water mark
>      - Average connection open time (or other similar stats)
>      - Number of connections force closed
>      - Limited list (with stack trace) of connections which kept conns
> open
>      - Limited list (with stack trace) of worst performing connections
>      - For each connection borrowed, show all its assests such as open
> result 
> sets, statements, the current query being exectued, is the query
> currently 
> being executed, how long has the query been running
> 
> 
> DBCP already exposed some of these stats. I first looked at dbcp a long
> time 
> ago when switching servlet engines where the old one provided a database
> pool 
> but I dodn't have time to retrofit my legacy code into dbcp. So I had to
> 
> write my own database pool which does much of the above (excluding JMX).
> While I rarely query the stats above - occasionally they are invaluable.
> 
> My 2 cents, but feel free to ignore me since I won't be able to help out
> in 
> the short term.
> 
> -Tim
> 
> Anton Tagunov wrote:
> > 
> > SK> Anybody know what Tomcat is using at this point?
> > Indeed would be interesting to see that :-)
> > 
> > - Anton
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org