[jboss-user] [JCA/JBoss] - Re: Configure no-tx-datasource: not to acquire shared lock

vickyk do-not-reply at jboss.com
Tue Jul 21 05:47:16 EDT 2009

"vigneshmpn" wrote :  I understand that though the read operations are not part of a transaction, the SELECT query would still acquire a shared lock on the data records read until the result is returned

I don't believe it to be the default behaviour, are you guessing this or you have tested it?

"vigneshmpn" wrote :  But most part of our business logic run as part of container-managed transaction, and so we don't want the read operations to be part of the transaction unnecessarily.

Using no-tx-datasource inside the Container managed transaction does not make any sense, also setting the transaction isolation level on the no-tx-datasource too would not make sense.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244905#4244905

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244905

More information about the jboss-user mailing list