Are you saying you have 100 concurrent threads hitting a database configured with a limit of 50 concurrent connections?
I would use dbcp over the builtin iBATIS one to see what happens. On Tue, 2006-11-14 at 02:49 +0800, class acts wrote: > Hi all, > > I'm using Jmeter to create 100 threads that in turn execute > queryForObject on the server side, it seems that if I try to do many > queryForObject calls from many threads concurrently, they all seem to > deadlock at popSession(). I'm using the builtin database pooler, > should I perhaps try using dbcp? Anyone run into this problem before? > I wouldn't mind having it timeout after n seconds if it can't execute > the query then I can just keep retrying. I hardly think postgresql > would like me to increase the concurrent connection count to more than > 50 (which I currently have it set at now). > > Thanks in advance
