framework like Spring can more
easily manage the transactions.
But iBATIS 2.x is designed around an assumption that is more heavily
dependent upon transactions. I would not recommend messing with that
assumption.
Clinton
From: Michael Schall [mailto:[EMAIL PROTECTED]
Sent: March-05-08 12:
;
> >
> >
> > int n = select count(*) from categories;
> >
> > List list = select * from categories;
> >
> >
> >
> > n == list.size() is only guaranteed if both statements were run in an
> > isolated transaction scope.
> >
> >
&
>
> For example (pseudocode):
>
>
>
> int n = select count(*) from categories;
>
> List list = select * from categories;
>
>
>
> n == list.size() is only guaranteed if both statements were run in an
> isolated transaction scope.
>
>
>
> Clinto
ope.
Clinton
From: Michael Schall [mailto:[EMAIL PROTECTED]
Sent: March-05-08 10:49 AM
To: user-java@ibatis.apache.org
Subject: Re: queryForList/Map/Object... rollbacks
I saw the commitRequired, but why are we creating the transaction in the
first place? Or is this a Sybase requirement that t
riginal Message-
From: Christopher Lamey [mailto:[EMAIL PROTECTED]
Sent: March-05-08 10:45 AM
To: user-java@ibatis.apache.org
Subject: Re: queryForList/Map/Object... rollbacks
Doh! Forgot about "commitRequired" - been using Spring for everything
lately.
Sorry about that.
On 3/
lbacks. If it was already set to false, it is entirely
> > possible that SimpleDataSource was entirely responsible for the
> aggressive
> > rollbacks -- thus we should probably make that configurable too.
> >
> > Clinton
> >
> > -Original Message-
> &
> possible that SimpleDataSource was entirely responsible for the aggressive
> rollbacks -- thus we should probably make that configurable too.
>
> Clinton
>
> -Original Message-
> From: Christopher Lamey [mailto:[EMAIL PROTECTED]
> Sent: March-04-08 5:07 PM
> To:
responsible for the aggressive
> rollbacks -- thus we should probably make that configurable too.
>
> Clinton
>
> -Original Message-
> From: Christopher Lamey [mailto:[EMAIL PROTECTED]
> Sent: March-04-08 5:07 PM
> To: user-java@ibatis.apache.org
> Subject: Re: query
h-04-08 5:07 PM
To: user-java@ibatis.apache.org
Subject: Re: queryForList/Map/Object... rollbacks
That is not the default iBATIS behavior, I'm guessing your container is
getting involved.
>From what I understand, the SIMPLE datasource type is generally for
standalone programs, not for apps
is this default behavior of iBatis to create a transaction and roll
> it back for even a select?
>
>
>
> Would JTA change this?
>
>
>
> Thanks,
>
> Tom
>
>
>
>
>
> -Original Message-
> From: Jeff Butler [mailto:[EMAIL P
?
Would JTA change this?
Thanks,
Tom
-Original Message-
From: Jeff Butler [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 04, 2008 3:53 PM
To: user-java@ibatis.apache.org
Subject: Re: queryForList/Map/Object... rollbacks
What transaction manager are you using?
Is this an EJB
What transaction manager are you using?
Is this an EJB application with CMT, or just a web application?
Have you read the information in the WIKI about configuring iBATIS on
WebSphere?
http://opensource.atlassian.com/confluence/oss/display/IBATIS/Environment+Specific+Information
Jeff Butler
On
We are performance monitoring our application and my DBA let me know
that we had over 3 MILLION rollbacks in a single day. We are using
WebSphere to DB2 on Win2k3 servers.
I looked in our code and could not find anything. Used p6spy and found
that every time queryForXXX is called I received a ro
13 matches
Mail list logo
