tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric J. Pinnell" <>
Subject Re: Oracle connection pooling
Date Sat, 09 Aug 2003 04:07:12 GMT

Firewalls, and I'm not speaking for all of them, as a rule of thumb close
_idle_ connections after an hour.

Your connections should be done well before that.


On Fri, 8 Aug 2003, Cristopher Daniluk wrote:

> We are running a fairly large ecommerce site consisting of 3 apache
> 2.0.48 servers being balanced between using UltraMonkey/ldirector and 2
> tomcat servers with AJP1.3. Everything is Linux except the back end
> which is a fairly hefty and firewalled Sun running Oracle8i.
> The webapps build a connection pool to oracle via the oracle.jdbc.pool.*
> connection pool. The pool instantiates fine and everything is great, but
> gradually the pool begins to break down. Idle connections are closed by
> Oracle (not sure if its oracle itself or the fw..), but the oracle pool
> doesn't figure it out. If someone happens to get the dead connection,
> Tomcat completely hangs on all threads until the session-timeout
> expires. Even the session replication code stops and the apache servers
> and the other tomcat in the cluster mark it offline. During the peak
> traffic it isn't so bad but at the end of the day after load goes back
> down, it's a big problem.
> We initially used DBCP but it didn't work for crap with Oracle. Is there
> a better pool to use with Oracle and Tomcat in a cluster environment and
> if not, is there a way we can get the Oracle pool to recycle some of
> these bad connections without blowing up the server?
> Thanks,
> Cris Daniluk
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message