Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Subject: RE: queryForObject deadlock with high concurrent calls
Date: Mon, 13 Nov 2006 20:24:11 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Message-ID: <50CA25BD6EEA954FA592C097399942E318C32898@CM1.wis.local>
Content-class: urn:content-classes:message
Thread-Topic: queryForObject deadlock with high concurrent calls
Thread-Index: AccHVGkcZKkhMo98RGiuJi/VBK5ImwABKidQ
From: "Niels Beekman" <n.beekman@wis.nl>
To: <user-java@ibatis.apache.org>

Check the maxSessions session in your SQLMap config. Also, do you really
mean deadlock? If so, there is something seriously wrong. Maybe you
could do a stack dump, I think it's just contention, not deadlock.

Niels

-----Original Message-----
From: class acts [mailto:classacts@gmail.com]=20
Sent: maandag 13 november 2006 19:49
To: user-java@ibatis.apache.org
Subject: queryForObject deadlock with high concurrent calls

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