Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
From: "Abdullah Kauchali" <abdullah.kauchali@isanusi.com>
To: <user-java@ibatis.apache.org>
Subject: RE: How does iBatis know which connection object to use from a pool?
Date: Thu, 8 Feb 2007 08:55:15 +0200
Organization: iSanusi Systems Architects
Message-ID: <000f01c74b4e$19e15ac0$0300a8c0@isanusid800>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <a10a823c0702070710v7029f7d0la40acd44ca143ff8@mail.gmail.com>
Thread-Index: AcdKyuwzoxaK6PbpRYyesQNJdLaq/gAglz/Q


Larry:
> 
> Almost, but not exactly. ;-)
> 
> The connection does not remain with the thread for the life of the
> thread, but rather the thread gets the connection from the pool (the
> pool marks it as used so no one else gets it), then uses it, then
> closes it (which just tells the pool that it can give it to others).

Cool, thanks - that makes sense.  :)

> I have not ever looked into if it checks for active transactions, I'd
> guess that the assumption is that they are clean.

I think it will be a great feature to throw an error if an attempt is made
to return a connection to the pool when it has a currently active
transaction - so, someone forgot to commit or rollback.  Just my 2c.