You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "Clinton Begin (JIRA)" <ib...@incubator.apache.org> on 2004/11/27 08:53:20 UTC

[jira] Closed: (IBATIS-10) Connections not released with JTA Transaction

     [ http://nagoya.apache.org/jira/browse/IBATIS-10?page=history ]
     
Clinton Begin closed IBATIS-10:
-------------------------------

      Assign To: Clinton Begin
     Resolution: Fixed
    Fix Version: 2.0.8

Added commitRequired attribute to transactionManager element.  This will force commit even on a query (for app servers that need it).

> Connections not released with JTA Transaction
> ---------------------------------------------
>
>          Key: IBATIS-10
>          URL: http://nagoya.apache.org/jira/browse/IBATIS-10
>      Project: iBatis for Java
>         Type: Bug
>   Components: SQL Maps
>     Reporter: Clinton Begin
>     Assignee: Clinton Begin
>      Fix For: 2.0.8

>
>  I'm using JTA with very basic configuration. I do many
> database transactions, like read-only, update, insert,
> and delete. In every operation I carefully add
> startTransaction(),
> commitTransaction() (for CRUD), and endTransaction() in
> my finally block. This is pretty normal iBATIS
> programming. I noticed that when many users/threads are
> accessing the application, it fails and container tells
> me that the connection pool has already been used up. I
> tried using External JTA transaction manager, and it
> seems to work fine. There seems to be a problem on how
> iBATIS handles connection/resource closing when JTA is
> used.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira