Connection Pool Woes

2006-03-24 Thread J.Talarczyk
Configuration: - Tomcat (1) 5.0.27 in dmz - Tomcat (2) 5.0.27 inside domain - Using JayBird DB Driver - IIS 6 - Interbase 7.5 DB server inside domain Tomcat (1) is currently having some serious issues with pooled connections to the db server. These applicaitons h

Re: Connection Pool Woes

2006-01-23 Thread Glen Mazza
Alex Turner wrote: Somehow I doubt the JSTL authors were so short sighted as not to release database connections properly. I'm sure they had production usage in mind when it was written, I'm just wondering how. Actually, they seemed to mostly have rapid prototyping in mind with the JSTL SQ

RE: Connection Pool Woes

2006-01-23 Thread Caldarale, Charles R
> From: Alex Turner [mailto:[EMAIL PROTECTED] > Subject: Re: Connection Pool Woes > > How does registering my pooling datasource with a naming directory > help connection management? It's doesn't - the JNDI suggestion is a red herring. Even with connection pooling, you

RE: Connection Pool Woes

2006-01-23 Thread GB Developer
ry 23, 2006 11:54 AM > To: Tomcat Users List > Subject: Re: Connection Pool Woes > > > How does registering my pooling datasource with a naming > directory help connection management? (Honest question - I > really don't know) > > Alex. > > On 1/23/06, Asad Hab

Re: Connection Pool Woes

2006-01-23 Thread Alex Turner
How does registering my pooling datasource with a naming directory help connection management? (Honest question - I really don't know) Alex. On 1/23/06, Asad Habib <[EMAIL PROTECTED]> wrote: > You should use JNDI with your connection pool to ensure that connections > are being managed appropriat

Re: Connection Pool Woes

2006-01-23 Thread Alex Turner
I'll just point out here that you actualy haven't pointed out any issue. I asked a question as to how, and you repsonded that it was an issue without ever explaing how, or if there even is a problem. Somehow I doubt the JSTL authors were so short sighted as not to release database connections pro

RE: Connection Pool Woes

2006-01-23 Thread Asad Habib
You should use JNDI with your connection pool to ensure that connections are being managed appropriately. - Asad On Mon, 23 Jan 2006, Chris McCormack wrote: Its poor practise to have a sql: jstl tag in production ready code. How do you deal with this when using pure JSTL sql calls using a

RE: Connection Pool Woes

2006-01-23 Thread Chris McCormack
Its poor practise to have a sql: jstl tag in production ready code. > How do you deal with this when using pure JSTL sql calls using a > connection? How does JSTL sql library release the connection at the > end of a page to ensure that connections don't get leaked? For reasons exactly like th

Re: Connection Pool Woes

2006-01-20 Thread Len Popp
nection, but some pages are pure JSP. > > Alex. > > On 1/20/06, Caldarale, Charles R <[EMAIL PROTECTED]> wrote: > > > > > > > -Original Message- > > > From: Alex Turner [mailto:[EMAIL PROTECTED] > > > Subject: Re: Connection Pool Woes &

Re: Connection Pool Woes

2006-01-20 Thread Alex Turner
ction, but some pages are pure JSP. Alex. On 1/20/06, Caldarale, Charles R <[EMAIL PROTECTED]> wrote: > > > > -Original Message- > > From: Alex Turner [mailto:[EMAIL PROTECTED] > > Subject: Re: Connection Pool Woes > > > > It looks like the connection

RE: Connection Pool Woes

2006-01-20 Thread Caldarale, Charles R
> -Original Message- > From: Alex Turner [mailto:[EMAIL PROTECTED] > Subject: Re: Connection Pool Woes > > It looks like the connection object was not being garbage collected > promptly (imagine that), and because it wasn't explicitly closed, it > was just

Re: Connection Pool Woes

2006-01-20 Thread Alex Turner
is > completed. The next thing may be to reduce the timeout interval of the > db connection pool. > > ND > > -Original Message- > From: Alex Turner [mailto:[EMAIL PROTECTED] > Sent: Friday, January 20, 2006 10:37 AM > To: users@tomcat.apache.org > Subject:

RE: Connection Pool Woes

2006-01-20 Thread Duan, Nick
pool. ND -Original Message- From: Alex Turner [mailto:[EMAIL PROTECTED] Sent: Friday, January 20, 2006 10:37 AM To: users@tomcat.apache.org Subject: Connection Pool Woes I am using Tomcat 5.5.12 on RedHat ES 4. I have a server that is set to maxThreads="5", maxSpareThreads=&qu

RE: Connection Pool Woes

2006-01-20 Thread Caldarale, Charles R
> From: Alex Turner [mailto:[EMAIL PROTECTED] > Subject: Connection Pool Woes > > I have a server that is set to maxThreads="5", maxSpareThreads="5", > and when I use a Simply Data Source, that does not pooling, if I hit > the page a lot, I get ove

Connection Pool Woes

2006-01-20 Thread Alex Turner
I am using Tomcat 5.5.12 on RedHat ES 4. I have a server that is set to maxThreads="5", maxSpareThreads="5", and when I use a Simply Data Source, that does not pooling, if I hit the page a lot, I get over 30 connections opened, with database connections that are not closing quickly at all. If thi