0 Replies Latest reply on Jun 22, 2006 2:07 PM by mpelzsherman

    possible problem with <transaction-isolation> setting

    mpelzsherman

      Just a general heads up: recently we added the following line to our datasource config files in an attempt to reduce deadlock errors from MS SQL Server 2000:

      <transaction-isolation>TRANSACTION_READ_UNCOMMITTED</transaction-isolation>

      After putting this in place, we started seeing major problems with blocking queries. I noticed a bunch of un-balanced "BEGIN TRAN" messages in SQL Profile just after "set transaction isolation mode" messages. So I think perhaps this setting was causing Jboss to leave a bunch of transactions open.

      I don't know if this is a bug in Jboss or what. Has anyone else experienced similar problems?