Page 1 of 1

problem with Transaction Scope Local

Posted: Sun 23 Oct 2011 19:05
by moticohen
Hey everyone,
we have a server application built against .net 4.0 running on a windows 2008 server, against oracle 11g with 11g client (nor direct mode). We are using the devart EF provider, and during a single request we open a few connections (creating a few contexts). We are using TransactionScope for transaction handling. Our problem started when we got an error from oracle about too many local sessions. We have searched for a solution and saw the Transaction Scope Local property in the connection string. We tried adding it to the connection string and now we get a null reference exception. Does anyone familiar with this?
This is the stack trace (null reference exception):

Devart.Common.DbConnectionInternal.EnlistToDistributedTransactionInternal(Transaction)
System.Data.EntityClient.EntityConnection.EnlistTransaction(Transaction)
System.Data.Objects.ObjectContext.SaveChanges(saveoptions)
MyCode()

Thanks

Posted: Tue 25 Oct 2011 16:43
by Shalex
Please specify your version (x.xx.xxx) of dotConnect for Oracle (the Tools > Oracle > About menu of VS) and your connection string (roughly, without credentials).

connection string

Posted: Wed 26 Oct 2011 08:23
by moticohen
Were using devart 6.50.228.0. Our connection looks like this:
User id=*;password=*;server=*;home=*;unicode=true;persist security info=true;transaction scope local=true
Thanks

Posted: Thu 27 Oct 2011 11:25
by Shalex
1. Try using the latest (6.50.237) version of dotConnect for Oracle. Does the problem persist in this case as well?
2. We cannot reproduce the error in our environment. Please localize the issue with NRE when using "Transaction Scope Local=true;" and send us a small test project with the corresponding DDL/DML script.

nre

Posted: Thu 27 Oct 2011 12:11
by moticohen
Hey, sorry for the ignorance, what is NRE?
Thanks

Posted: Thu 27 Oct 2011 12:30
by Shalex
NRE is an abbreviation for Null Reference Exception.