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 are going to inve
like expected.
-Kristen
On 8/15/09 7:46 AM, "Caldarale, Charles R"
wrote:
>> From: David Smith [mailto:d...@cornell.edu]
>> Subject: Re: Connection Pool Exhausted
>>
>> some other app on the same tomcat instance
>> is leaking the connections.
>
>
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
I know I'm coming late to the party and starting with the original post
to boot.
I see a third party app (not developed by Kristen) that ran perfectly
before a restart caused some problems. Given this, I'm of the feeling
there's a config problem OR some other app on the same tomcat instance
is le
> 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
> exhausted
> Does anyon
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
21 matches
Mail list logo
