logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bomb Diggy <techguy_chic...@yahoo.com>
Subject RE: JDBCAppender - log connection pooling code to db?
Date Thu, 13 Jun 2002 18:00:49 GMT
I'm confused about this.  I don't want to turn this
into a JDBC discussion, but are you saying that some
JDBC drivers magically hide *all* connection pooling
code somehow, and all I have to worry about is calling
getConnection() and closeConnection()?  In that case,
using JDBCAppender for logging really would be

What about Poolman and GenericDataSource(Struts) and
other pooling mechanisms?  Are they unnecessary if I'm
using the latest and greatest driver, from say Oracle?

Muy confused....

Goooooooooooooooooooool..........  :)

--- Thomas Tuft Muller <ttm@online.no> wrote:
> Btw, if your JDBC driver supports the javax.sql API
> it should be unnecessary
> to use your own pooling classes - the vendor has
> already written them for
> you.
> | -----Original Message-----
> | From: Bomb Diggy
> | My questions is whether it's possible, or just a
> | valid/good/bad practice, to try to log my
> connection
> | pooling mechanism code to the database as well.

Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup

To unsubscribe, e-mail:   <mailto:log4j-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-user-help@jakarta.apache.org>

View raw message