Try setting
<transactionManager type="JTA" *commitRequired="true"*>
...
</transactionManager>
Without this setting, iBATIS will not commit transactions (either automatic
or explicit) that only have selects in them. We see a similar issue on
WebSphere.
Jeff Butler
On 3/30/07, Mehul <[EMAIL PROTECTED]> wrote:
Hi
I was trying to work with JTA IBatis and WebLogic combination for my
persistence layer.
My configuration as below...
<transactionManager type="JTA">
<property name="UserTransaction"
value="javax.transaction.UserTransaction"/>
<dataSource type="JNDI">
<property name="DataSource" value="jdbc/pscdb"/>
</dataSource>
</transactionManager>
THe problem we are facing is that IBatis is creating new connection every
time and the pool gets evantually exhausted. We are not starting any
tansaction for select query but the connection is not released back to
pool.
the connections are only released after the connection time out period is
elasped.
Is it necessary to start transaction and end them even for select query?
Or
is there something more to be done to release the connection back to Pool.
Thanks,
--
View this message in context:
http://www.nabble.com/JTA-with-Ibatis-and-WebLogic-Server-tf3492356.html#a9753607
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
