Subject | RE: [Firebird-Java] Tomcat contexts and pooled connections |
---|---|
Author | Natal Vande Casteele |
Post date | 2003-06-18T08:13:38Z |
Hello,
Greetings,
Natal Vande Casteele
Software Engineer
Pocket and Soul
-----Original Message-----
From: Rick Fincher [mailto:rnf@...]
Sent: Tuesday, June 17, 2003 8:13 PM
To: Firebird-Java@yahoogroups.com
Subject: Re: [Firebird-Java] Tomcat contexts and pooled connections
Hi Natal,
Can you clarify a little on the pool? Are you using DBCP with Tomcat or
Jaybird's pooling mechanism?
If you are using DBCP you can set an "abandonded connection" parameter t
clean up stuff like this. It is a workaround, but it can be helpful.
Instructions are in the Tomcat documentation under the "JNDI DataSource
How-To" under the heading "Preventing DB Connection Pool Leaks".
Hope this helps!
Rick
> Are you using DBCP with Tomcat or Jaybird's pooling mechanism?I'm using Jaybird's pooling mechanism (FBWrappingDataSource).
> If you are using DBCP you can set an "abandonded connection" parameter tWe haven't looked into using DBCP yet. Maybe 'removeAbandoned' might indeed be a help.
> clean up stuff like this. It is a workaround, but it can be helpful.
> Instructions are in the Tomcat documentation under the "JNDI DataSource
> How-To" under the heading "Preventing DB Connection Pool Leaks".
Greetings,
Natal Vande Casteele
Software Engineer
Pocket and Soul
-----Original Message-----
From: Rick Fincher [mailto:rnf@...]
Sent: Tuesday, June 17, 2003 8:13 PM
To: Firebird-Java@yahoogroups.com
Subject: Re: [Firebird-Java] Tomcat contexts and pooled connections
Hi Natal,
Can you clarify a little on the pool? Are you using DBCP with Tomcat or
Jaybird's pooling mechanism?
If you are using DBCP you can set an "abandonded connection" parameter t
clean up stuff like this. It is a workaround, but it can be helpful.
Instructions are in the Tomcat documentation under the "JNDI DataSource
How-To" under the heading "Preventing DB Connection Pool Leaks".
Hope this helps!
Rick
----- Original Message -----
> Hello,
>
> We're currently using the latest Firebird-Java driver release (with
> pooled connections) with Firebird 1.0.3 CS and Tomcat 4.
>
> Everything is working smoothly, except for the fact that when we restart
> a servlet context (via the Tomcat application manager), the connections
> are not returned to the pool (a 'netstat -a | grep "gds"' confirms
> this). Restarting the complete tomcat server solves the problem (returns
> all connections) but this is not desired as all our servlet-contexts
> will be offline for a second or 5. Reloading a context via the
> application manager is almost instantaneous.
>
> Is there a way to return the database connections to the pool when the
> servlet context is reloaded? I presume they're removed from memory and
> reloaded but different from restarting the tomcat server, the
> connections aren't returned.
>
> Greetings,
> Natal Vande Casteele
> Software Engineer
> Pocket and Soul
Yahoo! Groups Sponsor
To unsubscribe from this group, send an email to:
Firebird-Java-unsubscribe@yahoogroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.