No, you don't have to use start/commit/end with selects -- but it is faster
and will give you more reliable data if you have multiple related selects.
A switch from a throttle increment problem to a connection pool problem is
pretty much a guarantee that somewhere in your code a transaction is not
A couple of months ago, we experimented the same problem.
We upgraded to ibatis 2.3.4 / ibatis dao 2.2.0 as you recommended and the
throttle error disappeared. However, we are getting now an error with the
connection pool (we use the jboss datasource via ibatis): “there are no more
connections av
gt; --
> *From:* Clinton Begin [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, March 18, 2008 14:17
> *To:* user-java@ibatis.apache.org
> *Subject:* Re: IBATIS-496: indefinite wait in Throttle.increment()
>
> You're likely not closing off your sessions con
-java@ibatis.apache.org
Subject: Re: IBATIS-496: indefinite wait in Throttle.increment()
You're likely not closing off your sessions consistently. Try running
iBATIS from the SVN trunk. I've removed Throttle from the core, thus you
should now get a better error (or at least I hope
You're likely not closing off your sessions consistently. Try running
iBATIS from the SVN trunk. I've removed Throttle from the core, thus you
should now get a better error (or at least I hope you do!). I'm guessing
the new error will be from your datasource complaining that you're out of
connec
Hi!
We have a web application running on Tomcat, using the Commons JDBC
connection pool and iBatis 2.2. Our app uses a single "SqlMapClient"
instance for all our database access. After 7-10 days, the application
doesn't have any database connections anymore. At first we thought we're
running out
