Re: Analyzing Connection Pool Errors/Leaks

2013-04-02 Thread David Landis
ion seulement 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. > > > > > > Subject: Re: Analyzing Connec

Re: Analyzing Connection Pool Errors/Leaks

2013-04-02 Thread chris derham
> OK, I'll have to investigate the DB setting more thoroughly. The maximum > sessions and processes in Oracle are higher than we were using for the test > though (several hundred). We hit a similar situation a year ago. Essentailly Oracle has a TNS listener process that accepts connections. This i

RE: Analyzing Connection Pool Errors/Leaks

2013-04-02 Thread Martin Gainty
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. > Subject: Re: Analyzing Connection Pool Errors/Leaks > From: dmik...@vmware.com &g

Re: Analyzing Connection Pool Errors/Leaks

2013-04-01 Thread Daniel Mikusa
On Apr 1, 2013, at 4:18 PM, David Landis wrote: > Thanks for the response, see my comments inline below. > > > On Mon, Apr 1, 2013 at 3:49 PM, Daniel Mikusa wrote: > >> On Apr 1, 2013, at 3:31 PM, David Landis wrote: >> >>> Hi guys, >>> >>> When running a performance test on my system it sta

Re: Analyzing Connection Pool Errors/Leaks

2013-04-01 Thread David Landis
Thanks for the response, see my comments inline below. On Mon, Apr 1, 2013 at 3:49 PM, Daniel Mikusa wrote: > On Apr 1, 2013, at 3:31 PM, David Landis wrote: > > > Hi guys, > > > > When running a performance test on my system it starts fine, but after a > > while I start getting errors in my ap

Re: Analyzing Connection Pool Errors/Leaks

2013-04-01 Thread Daniel Mikusa
On Apr 1, 2013, at 3:31 PM, David Landis wrote: > Hi guys, > > When running a performance test on my system it starts fine, but after a > while I start getting errors in my application log such as (see the bottom > for full stack trace): > > 2013-03-29 16:38:54,778 ERROR > [org.hibernate.engine.