Under the covers, tomcat does use DBCP , but refractors the package name
to avoid collisions with the real DBCP package.
--David
Mikolaj Rydzewski wrote:
Christopher Schultz wrote:
From your DataSource configuration, it looks like you are using the
Oracle driver directly. Does that have built
Mikolaj Rydzewski wrote:
But, reading the config for the second time I can not find any
references to dbcp classes! Just DataSource interface and jdbc driver
class name. So - does this configuration uses connection pooling (how
could it be?)
I'll answer to my question ;-)
Quoting DBCP wiki:
"
Christopher Schultz wrote:
From your DataSource configuration, it looks like you are using the
Oracle driver directly. Does that have built-in pooling?
The original problem is solved, but I'm a little confused now.
Posted configuration was exactly the same like the examples on Tomcat
website:
On 10/12/06, DE VINZELLES, Guillaume (ext.)
<[EMAIL PROTECTED]> wrote:
Hello,
One of our connections wasn't properly closed, as you said.
You fixed the problem and now everything is running fine.
Great !
"Un grand classique" ;-)
Pascal
---
ssage d'origine-
De : Richard DeGrande [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 11 octobre 2006 17:58
À : Tomcat Users List
Objet : Re: JDBC Pool exhaustion
Martin,
Isn't dbcp connection pooling ?? I think I am missing something, I am
not clear on why you are advocating a s
ssage -
From: "Christopher Schultz" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Wednesday, October 11, 2006 10:54 AM
Subject: Re: JDBC Pool exhaustion
-
To start a new topic, e-mail: user
Objet : Re: JDBC Pool exhaustion
If you have 1000 connections then you would be well advised to use connection
pooling
more specifically you need to separate the activities of
settingup a connection from
getting the connection
you also need to separate the activities of
freeing the conne
0 18 21 64
-Message d'origine-
De : Christopher Schultz [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 11 octobre 2006 16:55
À : Tomcat Users List
Objet : Re: JDBC Pool exhaustion
Guillaume,
> For Christopher and Alberty, here is an example of how we connect to the
> database.
&g
Message -
From: "Christopher Schultz" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Wednesday, October 11, 2006 10:54 AM
Subject: Re: JDBC Pool exhaustion
Il giorno mer, 11/10/2006 alle 16.02 +0200, DE VINZELLES, Guillaume
(ext.) ha scritto:
> Hello there,
>
> We are running a Tomcat 5.5.17 on a Sun Solaris system (SunFire V240) with a
> Sun JVM 1.5, and we are facing unavoidable JDBC pool exhaustions. We are
> using an Oracle 9i database.
>
> He
Seems to be good except:
finally {
try {
if (result != null) {
result.close();
result = null;
}
if (oCmd != null) {
oCmd.close();
oCmd = null;
Guillaume,
> For Christopher and Alberty, here is an example of how we connect to the
> database.
> I'm quite sure we are using the JDBC pool.
From your DataSource configuration, it looks like you are using the
Oracle driver directly. Does that have built-in pooling? If not, it
looks like you m
JDBC Pool exhaustion
DE VINZELLES, Guillaume (ext.) wrote:
> finally {
> try {
> if (result != null) {
> result.close();
> result = null;
> }
> if (oCmd != null) {
>
DE VINZELLES, Guillaume (ext.) wrote:
finally {
try {
if (result != null) {
result.close();
result = null;
}
if (oCmd != null) {
oCmd.close();
oC
}
}
Guillaume de Vinzelles
DSI/PFS Neuf Cegetel
Altran Technologies
[EMAIL PROTECTED]
01 70 18 21 64
-Message d'origine-
De : Christopher Schultz [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 11 octobre 2006 16:20
À : Tomcat Users List
Objet : Re: JDBC Pool exhaustion
G
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Pascal Alberty
Envoyé: mercredi 11 octobre 2006 16:10
À: Tomcat Users List
Objet: Re: JDBC Pool exhaustion
Check your code to unclosed connections (and statments) first !
On 10/11/06, DE VINZELLES, Guillaume (ext.)
<[EMAIL PROTECTED]>
Guillaume,
> type="javax.sql.DataSource"
> driverClassName="oracle.jdbc.driver.OracleDriver"
>
> The Tomcat manager shows around 1000 sessions on the server, which
> seems to be pertinent.
What is your connection allocation strategy? Meaning: do you allocate a
Connection object to each session
ELLES, Guillaume (ext.)" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, October 11, 2006 10:02 AM
Subject: JDBC Pool exhaustion
Hello there,
We are running a Tomcat 5.5.17 on a Sun Solaris system (SunFire V240) with a
Sun JVM 1.5, and we are facing unavoidable JDBC pool exhaustions.
D] [mailto:[EMAIL PROTECTED] De la part de Pascal Alberty
Envoyé : mercredi 11 octobre 2006 16:10
À : Tomcat Users List
Objet : Re: JDBC Pool exhaustion
Check your code to unclosed connections (and statments) first !
On 10/11/06, DE VINZELLES, Guillaume (ext.)
<[EMAIL PROTECTED]> wrote:
>
Check your code to unclosed connections (and statments) first !
On 10/11/06, DE VINZELLES, Guillaume (ext.)
<[EMAIL PROTECTED]> wrote:
Hello there,
We are running a Tomcat 5.5.17 on a Sun Solaris system (SunFire V240) with a
Sun JVM 1.5, and we are facing unavoidable JDBC pool exhaustions. We
Hello there,
We are running a Tomcat 5.5.17 on a Sun Solaris system (SunFire V240) with a
Sun JVM 1.5, and we are facing unavoidable JDBC pool exhaustions. We are using
an Oracle 9i database.
Here is the JDBC entry from our server.xml:
The Tomcat manager shows around 1000 sessions on the ser
21 matches
Mail list logo
