Did anyone had a chance to look into my query ? This is causing a major issue with the application I am working on in production and any help is highly appreciated.
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. [EMAIL PROTECTED] 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: http://www.nabble.com/Connection-Parameters-for-JDBC-transaction-Manager-tp15139583p15183322.html Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
