Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ericblue76@gmail.com designates
 64.233.166.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=tN3Ov6PGtbxKIziV5KieuXuPonnOUX/eBF08z/90rjO9zlnKndPuzBduKeOhtZBudysEvkX7n2XpfcfsktO/FycuSNcKX3tN45gX0Ntg9SOxuCw3QVUODmiEnpJDgIjfPDmDRvvm3JS9SINUGRocakkbBnyTXAWTTdg9l20IxPI=
Message-ID: <295517f10606091813h147ff079pd5c699f084fc8d43@mail.gmail.com>
Date: Fri, 9 Jun 2006 18:13:25 -0700
From: "Eric T. Blue" <ericblue76@gmail.com>
To: user-java@ibatis.apache.org
Subject: Re: Help with understanding transaction behavior with multiple
 threads
In-Reply-To: <295517f10606051637y782b31fbr9b83a058ea62ff4d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_12902_24979478.1149902005086"
References: <295517f10606051637y782b31fbr9b83a058ea62ff4d@mail.gmail.com>

------=_Part_12902_24979478.1149902005086
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

No takers on this one?


On 6/5/06, Eric T. Blue <ericblue76@gmail.com> wrote:
>
> Hi,
>
> I want to find out the easiest possible way to start a transaction, create
> a thread that performs DAO inserts, and still have the newly created thread
> honor the start and end transaction from the launching application.
>
> I'm working on a project where I'm using iBatis DAO with SQLMAP as my
> transaction manager.  Up until this point transactions and rollbacks work
> fine.
>
> daoManager.startTransaction();
>
> try {
>     service.createObject (a);
>
>     daoManager.commitTransaction();
>
> } catch (ServiceException e) {
>     // Handle exception
> } finally {
>
>     daoManager.endTransaction();
> }
>
> I now have a situation where instead of calling service.createObject()
> directly I'm creating an encapsulated unit of work and running with a new
> thread.  What I've discovered is that whenever an exception is thrown, the
> create Object exists in the database, although commitTransaction has never
> been called.  After browsing through the mailing list, and eventually the
> code, I discovered that the dao manager (DaoContext) is using ThreadLocal to
> keep track of transaction and state.  Given this fact, is it even possible
> to solve my problem without having to change the underlying code or right
> some sort of wrapper class.
>
> What I'm a little confused about is that default autocommit is set to
> false.  If the launched thread performs the INSERT, even though it is
> unaware that start transaction and end transaction are happening, why is the
> record being committed?  Any help would be appreciated.
>

------=_Part_12902_24979478.1149902005086
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

No takers on this one?<br><br><br><div><span class="gmail_quote">On 6/5/06, <b class="gmail_sendername">Eric T. Blue</b> &lt;<a href="mailto:ericblue76@gmail.com">ericblue76@gmail.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Hi,<br><br>I want to find out the easiest possible way to start a transaction, create a thread that performs DAO inserts, and still have the newly created thread honor the start and end transaction from the launching application. 
<br><br>I'm working on a project where I'm using iBatis DAO with SQLMAP as my transaction manager.&nbsp; Up until this point transactions and rollbacks work fine.<br><br>daoManager.startTransaction();<br><br>try {<br>&nbsp;&nbsp;&nbsp; service.createObject

(a);<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; daoManager.commitTransaction();<br><br>} catch (ServiceException e) {<br>&nbsp; &nbsp; // Handle exception<br>} finally {<br><br>&nbsp;&nbsp;&nbsp; daoManager.endTransaction();<br>}&nbsp;  <br><br>I now have a situation where instead of calling 
service.createObject() directly I'm creating an encapsulated unit of work and running with a new thread.&nbsp; What I've discovered is that whenever an exception is thrown, the create Object exists in the database, although commitTransaction has never been called.&nbsp; After browsing through the mailing list, and eventually the code, I discovered that the dao manager (DaoContext) is using ThreadLocal to keep track of transaction and state.&nbsp; Given this fact, is it even possible to solve my problem without having to change the underlying code or right some sort of wrapper class.
<br><br>What I'm a little confused about is that default autocommit is set to false.&nbsp; If the launched thread performs the INSERT, even though it is unaware that start transaction and end transaction are happening, why is the record being committed?&nbsp; Any help would be appreciated.
<br>

</div></blockquote></div><br>

------=_Part_12902_24979478.1149902005086--