ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clinton Begin" <clinton.be...@gmail.com>
Subject RE: Connection Parameters for JDBC transaction Manager
Date Wed, 30 Jan 2008 16:33:43 GMT
+1 to Jeff, those settings have already been removed from the trunk. 


Use EXTERNAL if you're using EJB or Spring (or any other transaction capable
container), or JTA if you're using iBATIS alone with XA connections.
Otherwise, using JDBC should work fine too.






From: Jeff Butler [mailto:jeffgbutler@gmail.com] 
Sent: January-30-08 8:41 AM
To: user-java@ibatis.apache.org
Subject: Re: Connection Parameters for JDBC transaction Manager


We recommend getting rid of maxRequests, maxSessions, maxTransactions -
these values will no longer be supported in the next version of iBATIS.  In
your case (using a JNDI connection pool with WebSphere), you should set all
these things on the datasource configuration in WebSphere.


Also, it's probably best to use EXTERNAL or JTA transacation manager with
WebSphere (depending on whether you are using CMT or not) - see the
information in this WIKI page for examples:




Jeff Butler

On Jan 30, 2008 9:00 AM, venkatesh_ngl@rediffmail.
<venkatesh_ngl@rediffmail.com> wrote:

Did anyone had a chance to look into my query ? This is causing a major
with the application I am working on in production and any help is highly

BTW , the transaction is defined as CMP and we use websphere 5.1 as
application server.

Let me know if anyone has faced similar kind of issues in the past.

venkatesh_ngl@rediffmail. wrote:
> I have another question. If I have a file where sqlmapconfig.xml I have
> mentioned it as       <transactionManager type="JDBC" >
>               <dataSource type="JNDI">
>                       <property name="DataSource" value="jdbc/abcd"/>
>               </dataSource>
>       </transactionManager>
> Would the connection parameters set in sqlmapconfig.xml would come into
> affect ? I tried changing the parameters to default values in setting
> section but it caused a major problems with connections. The application
> was not able to handle those many connections
> The setting was as follows
> <settings
>               cacheModelsEnabled="false"
>               enhancementEnabled="true"
>               lazyLoadingEnabled="true"
>               errorTracingEnabled="true"
>               useStatementNamespaces="false"
>                           maxRequests="512"
>               maxSessions="128"
>               maxTransactions="32"
>       />
> Which connection parameters would come into affect? The one that is
> mentioned in sqlmapconfig.xml or the parameters associated with JNDI
> configurations ?


View this message in context:

Sent from the iBATIS - User - Java mailing list archive at Nabble.com
<http://nabble.com/> .


View raw message