lement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Fri, 21 Aug 2009 09:10:51 -0700
> Subject: Re: Connection Pool
I just wanted to report back on the connection pool exhausted issue. I got
some help from the JASIG uPortal list and it turns out that some of my
settings in the uPortal config files were screwing with the way database
connection pooling was working. Now that those settings have been tweaked,
it
--- On Mon, 8/17/09 at 11:38 AM, Kristen Walker wrote:
> We had some help debugging the connection pool exhausted issue over the
> weekend and for now it seems that changing jdbcUsePool=true to
> jdbcUsePool=false stops the site from crashing due to connection pool
> issues. We
We had some help debugging the connection pool exhausted issue over the
weekend and for now it seems that changing jdbcUsePool=true to
jdbcUsePool=false stops the site from crashing due to connection pool
issues. We are going to investigate more to see why connection pooling
isn't working
On Sat, Aug 15, 2009 at 7:08 AM, wrote:
> Okay, so let's say I set my db connection pool size to one, where do I look
> to see what connection doesn't get closed like it should?
Chuck already gave you the sophisticated (thread dump) approach.
Alternatively, from the Department of Quick Hackery :
> From: David Smith [mailto:d...@cornell.edu]
> Subject: Re: Connection Pool Exhausted
>
> some other app on the same tomcat instance
> is leaking the connections.
Can't be another app - the connections are declared local to this webapp.
As David states, finding out wha
ption
> is org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool
> exhausted
>
> I have been troubleshooting this for weeks now. I have updated the mysql
> connector driver from mysql-connector-java-3.1.12-bin.jar to
> mysql-connector-java-5.1.8-bin.jar. We wer
> From: kwal...@sbceo.org [mailto:kwal...@sbceo.org]
> Subject: RE: Connection Pool Exhausted
>
> where do I look to see what connection doesn't get closed
> like it should?
Now you've reached the hard part. You'll need to take thread dumps to find out
what thre
these are really obvious, I'm new to this.
Thanks!
Kristen
Quoting "Caldarale, Charles R" :
From: Martin Gainty [mailto:mgai...@hotmail.com]
Subject: RE: Connection Pool Exhausted
from my experience setting numActive to 1 is NOT a l/t solution
No one ever suggested it was
> From: Martin Gainty [mailto:mgai...@hotmail.com]
> Subject: RE: Connection Pool Exhausted
>
> from my experience setting numActive to 1 is NOT a l/t solution
No one ever suggested it was; it's simply a debugging technique to make it
easier to find the connection leak.
100
> From: ma...@apache.org
> To: users@tomcat.apache.org
> Subject: Re: Connection Pool Exhausted
>
> Martin Gainty wrote:
> > set numActive=1 is not a long term solution mark
>
> It isn't meant to be. For the umpteenth time, read the
Martin Gainty wrote:
> set numActive=1 is not a long term solution mark
It isn't meant to be. For the umpteenth time, read the thread and
understand the context before you comment.
Mark
-
To unsubscribe, e-mail: users-unsubscr
; From: ma...@apache.org
> To: users@tomcat.apache.org
> Subject: Re: Connection Pool Exhausted
>
> Martin Gainty wrote:
> > that is only one solution
>
> No it isn't. You didn't answer the question asked which was "How do I
> set the connection pool size to 1&quo
Martin Gainty wrote:
> that is only one solution
No it isn't. You didn't answer the question asked which was "How do I
set the connection pool size to 1".
> what is your non-jocl solution?
Read the thread. Hassan has already answered the question.
Mark
---
100
> From: ma...@apache.org
> To: users@tomcat.apache.org
> Subject: Re: Connection Pool Exhausted
>
> Martin Gainty wrote:
> > dbcp parameters are located in a *.jocl file located on your classpath
>
> Kristen - you can safely ignore this. It doesn't apply in your case
Martin Gainty wrote:
> dbcp parameters are located in a *.jocl file located on your classpath
Kristen - you can safely ignore this. It doesn't apply in your case.
Martin - Please read the entire thread before you post. It was made
quite clear how the pool was configured and it wasn't with a jocl
> From: kwal...@sbceo.org
> To: users@tomcat.apache.org
> Subject: Re: Connection Pool Exhausted
>
> Sorry if this is a stupid question, I am pretty new to this, but how do I set
> the db connection pool size to 1?
>
> Thanks,
> Kristen
>
> Quoting Hassan Schroed
On Fri, Aug 14, 2009 at 6:04 PM, wrote:
> how do I set the db connection pool size to 1?
--
Hassan Schroeder hassan.schroe...@gmail.com
twitter: @hassan
-
To unsubscribe, e-mail: users-unsubscr...@t
Sorry if this is a stupid question, I am pretty new to this, but how do I set
the db connection pool size to 1?
Thanks,
Kristen
Quoting Hassan Schroeder :
On your test/staging server, set your db connection pool size to 1
and exercise the site; if there's a connection leak, you'll find it pret
On Fri, Aug 14, 2009 at 5:21 PM, wrote:
>
> Caused by: org.springframework.dao.DataAccessResourceFailureException:
> RDBMServices sql error trying to get connection to uportal; nested exception
> is org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool
> ex
:
RDBMServices sql error trying to get connection to uportal; nested exception
is org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool
exhausted
I have been troubleshooting this for weeks now. I have updated the mysql
connector driver from mysql-connector-java-3.1.12-bin.jar to
Kristen Walker wrote:
> Hi everyone,
Please don't hijack threads.
Mark
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool
exhausted
I have been troubleshooting this for weeks now. I have updated the mysql
connector driver from mysql-connector-java-3.1.12-bin.jar to
mysql-connector-java-5.1.8-bin.jar. We were running on a Feisty Fawn box -
I reinstalled
ere a way
>> to
>> print stack trace the current active connections or something to find
>> where
>> it's leaky?
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For add
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arrow,
On 6/17/2009 10:44 AM, Arrowx7 wrote:
> Using mysql JDBC driver. Somewhere in the appilcation, the connections are
> drawn from the DBCP pool, and never returned. I did
> dataSource.getNumActive() and dataSource.getNumIdle(). There are 2 idl
set properties
removeAbandoned="true"
removeAbandonedTimeout="60"
logAbandoned="true"
This will expire leaked connections and print out the stack trace from
where they were acquired.
Filip
Arrowx7 wrote:
Using mysql JDBC driver. Somewhere in the appilcation, the connections are
drawn from
users@tomcat.apache.org
Subject: DBCP connection pool exhausted, can I trace borrowed connnections from
pool?
Using mysql JDBC driver. Somewhere in the appilcation, the connections are
drawn from the DBCP pool, and never returned. I did
dataSource.getNumActive() and dataSource.getNumIdle().
close the connection and return it to pool. there a way to
print stack trace the current active connections or something to find where
it's leaky?
--
View this message in context:
http://www.nabble.com/DBCP-connection-pool-exhausted%2C-can-I-trace-borrowed-connnections-from-pool--tp24075241p240
Cc :
Date : Sat, 21 Apr 2007 10:08:21 +0200
Subject : Cannot get a connection, pool exhausted
> Hello,
> i'm trying to achieve DBCP with tomcat 5.5.9. I thought to have done things right since
the application could connect to db, but after a night that the application w
//
}
}
}
is there anything else i should change for getting the pool connection to work?
Thanks in advance.
-- Initial Header ---
From : "[EMAIL PROTECTED]" [EMAIL PROTECTED]
To : "users" users@tomcat.apache.org
Cc
On 4/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
is there anything else i should change for getting the pool connection to work?
Thanks in advance.
Most of the best practices and common mistakes to avoid are covered
here:
http://tomcat.apache.org/tomcat-5.0-doc/jndi-datasource-exampl
-- Initial Header ---
>From : "[EMAIL PROTECTED]" [EMAIL PROTECTED]
To : "users" users@tomcat.apache.org
Cc :
Date : Sat, 21 Apr 2007 10:08:21 +0200
Subject : Cannot get a connection, pool exhausted
> Hello,
> i'm trying to
Hello,
i'm trying to achieve DBCP with tomcat 5.5.9. I thought to have done things
right since the application could connect to db, but after a night that the
application was running, in the morning, in logs, i saw a lot of "Cannot get a
connection, pool exhausted" err
Thanks for the reply...
-Original Message-
From: Steve Kirk [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 27, 2005 12:07 PM
To: 'Tomcat Users List'
Subject: RE: Error: Cannot get a connection, pool exhausted
yes. in the same place you have set maxActive etc.
>
yes. in the same place you have set maxActive etc.
> -Original Message-
> From: KUMAR, NANDA [AG-Contractor/1000]
> [mailto:[EMAIL PROTECTED]
> Sent: Thursday 27 October 2005 15:46
> To: 'Tomcat Users List'
> Subject: RE: Error: Cannot get a connection, p
Thanks Jan, Let me try this. I need to add these parameters in context.xml?
Am I right?
Thanks
Nanda
-Original Message-
From: Jan Pernica [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 27, 2005 1:49 AM
To: Tomcat Users List
Subject: Re: Error: Cannot get a connection, pool exhausted
st place to call the close()
method is in a finally() block.
-Original Message-
From: KUMAR, NANDA [AG-Contractor/1000]
[mailto:[EMAIL PROTECTED]
Sent: Wednesday 26 October 2005 16:13
To: users@tomcat.apache.org
Subject: Error: Cannot get a connection, pool exhausted
Frequently we we
26, 2005 12:09 PM
To: 'Tomcat Users List'
Subject: RE: Error: Cannot get a connection, pool exhausted
IMHO I would say that you just need to rearrange your code a little - I
would move some code that you have in the try{} block to a finally{} block,
so that it gets executed whether or
catch (Exception finEx4)
{/*ignore*/}
}
conn = null;
}
}
> -Original Message-
> From: KUMAR, NANDA [AG-Contractor/1000]
> [mailto:[EMAIL PROTECTED]
> Sent: Wednesday 26 October 2005 16:56
> To: 'To
, 2005 10:35 AM
To: 'Tomcat Users List'
Subject: RE: Error: Cannot get a connection, pool exhausted
how many concurrent requests are you handling? you have configured
> maxActive
> 100
so as soon as 100 concurrent conns are reached, you will exhaust the pool.
If
. The best place to call the close()
method is in a finally() block.
> -Original Message-
> From: KUMAR, NANDA [AG-Contractor/1000]
> [mailto:[EMAIL PROTECTED]
> Sent: Wednesday 26 October 2005 16:13
> To: users@tomcat.apache.org
> Subject: Error: Cannot get
Frequently we were getting "Cannot get a connection, pool exhausted" error
on production. I know in our application, we are closing the connection
after each connection. Here is our context.xml parameters and values. We set
maxActive connection to 100. Please let me know what we are doin
42 matches
Mail list logo
