BUG Exclusive connections for request. Persistent MSSQL Isolation Level.

Description

Hi,
found that Setting once transaction isolation level, it is persistent, for this connection, till next change of it, or reboot.

"Exclusive connections for request" is set ON.

In ACF10 and ACF18 it works properly. Isolation level is set only for one request then is changing back.

 

Workaround would be to set isolation level back to “read committed” in every query that change connection state, and to catch errors (ex. timeout) to set back read committed state.

In this catch clause we should find, get and use only connection that was used for changing connection state.

 

Using SQL profiler I found that:

  1. ACF

    1. send before every request “SET TRANSACTION ISOLATION LEVEL READ COMMITTED“

    2. send request

    3. Send after every request 2 requests “SET TRANSACTION ISOLATION LEVEL READ COMMITTED“

  2. Lucee

    1. just send request.

Now, I don’t know how to proceed. Will it be implemented in Lucee, or I should change it in my project?

 

Environment

Microsoft SQL Server 2014
Windows Server 2012

Status

Assignee

Unassigned

Reporter

Guardian

Labels

None

Affects versions

Priority

Blocker
Configure