Hello all,
I've been using iBATIS for a while quite successfully with a
transactionManager type of "JDBC" - however, I now want to use JTA and
am not having so much luck.
I have a block of code like this:
// start a transaction
dao.startTransaction();
// get and update a
On 08/04/2008, Alistair Young <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I've been using iBATIS for a while quite successfully with a
> transactionManager type of "JDBC" - however, I now want to use JTA and
> am not having so much luck.
>
> [ ... snip ...]
>
> Can anybody help? I think I must
Hello again,
After figuring out my previous problem, I've got my iBATIS/JTA test
application working up to a point (start transaction, update followed
by end or commit).
Now, according to the book "iBATIS in Action", when configured to use
a JTA transactionManager, "iBATIS will look for the globa
Once again I seem to have found a solution shortly after asking the question...
On 08/04/2008, Alistair Young <[EMAIL PROTECTED]> wrote:
> [ ... snip ... ]
>
>// start a transaction
>// [iBATIS starts a new JTA transaction...?]
>sqlMapClient.startTransaction();
>
>/
iBATIS does not support nested transactions. Take a look at the class
com.ibatis.sqlmap.engine.transaction.jta.JtaTransaction
to see what's going on.
If a JTA transaction already exists...
1. The iBATIS "startTransaction" will not start another transaction
2. The iBATIS commit does nothing
3. Th
I usually suggest just using the EXTERNAL transaction manager and let your
container manage the transaction entirely. I'm pretty sure this works well
for most people.
Clinton
On Tue, Apr 8, 2008 at 10:18 AM, Jeff Butler <[EMAIL PROTECTED]> wrote:
> iBATIS does not support nested transactions.
Eventually my aplication server is going down by "Out of Memory". Analizing
de heap dumping, it's point for the same class allocating 600 Mb.
This event can occur 3 hours or 3 days after I restart my server. This class
is used thounsands times in the period. Monitoring the memory of the server,
I
Try disabling "enhancement" as well. It might be CGLIB.
Clinton
On Tue, Apr 8, 2008 at 6:51 AM, Fernando Simonetti <[EMAIL PROTECTED]>
wrote:
> Eventually my aplication server is going down by "Out of Memory".
> Analizing
> de heap dumping, it's point for the same class allocating 600 Mb.
>
> T
It seems like there is not enough data in your mail...
what data base are you accessing? how are you dealing with it (DataSource is
JDBC or via the App Server) your class is keeping the data for any reason
(maybe in a session or application bean)? what's the App Server?
etc, etc... if i were you
