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 i
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
From: Larry Meadors [EMAIL PROTECTED]:
>All connectins and transactions are managed using thread local
>storage, so each thread has it's own connection, etc..
(Thanks Larry!)
Ok. Understood. So, each time a new thread that uses SqlMapClientImpl is
spawned, a Connection object is removed
All connectins and transactions are managed using thread local
storage, so each thread has it's own connection, etc..
Larry
On 2/7/07, Abdullah Kauchali <[EMAIL PROTECTED]> wrote:
As I understand it, SqlMapClientImpl (SqlMapClient) hides or wraps the primary
JDBC object, Connection. So, we c
