Page 1 of 1

NullReferenceException inside EnlistToDistributedTransaction

Posted: Wed 21 Mar 2012 10:15
by Lukas
Hello,

we get a NullReferenceException exception inside this method:
Devart.Common.DbConnectionInternal.EnlistToDistributedTransactionInternal(Transaction transaction)

We don't really know, why this happens.
The Devart.Data.Oracle.dll version is 6.70.311.0
It's inside a dllhost.exe process (COM+) running with inactive user.
Maybe you can get us a hint what to do here.

The call stack is:
System.NullReferenceException: Object reference not set to an instance of an object.
at Devart.Common.DbConnectionInternal.EnlistToDistributedTransactionInternal(Transaction transaction)
at Devart.Common.DbConnectionInternal.EnlistToDistributedTransaction(Transaction transaction)
at Devart.Common.DbConnectionBase.EnlistTransaction(Transaction transaction)
at System.Data.EntityClient.EntityConnection.EnlistTransaction(Transaction transaction)
at System.Data.Objects.ObjectContext.EnsureConnection()
at System.Data.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)
at System.Data.Objects.ObjectQuery`1.System.Collections.Generic.IEnumerable.GetEnumerator()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at DataEngine.Entity.EntityPersistenceContext.Helpline.BusinessLayer.DataModel.Persistence.IQueryCases.GetNotClosedServiceUnitIds(Int32 id, String defName)

Posted: Thu 22 Mar 2012 10:36
by Lukas
Hello,

using the 6.50.250 version of the Devart.Data.Oracle.dll the NullReferenceException don't occur.
So there have been propably a change that is really suboptimal.

Posted: Fri 23 Mar 2012 14:09
by Shalex
Could you please try using the latest (6.80.325) version of dotConnect for Oracle? If the problem persists with 6.80.325 as well, send us a small test project with the corresponding DDL/DML script to reproduce the issue in our environment.

Posted: Thu 29 Mar 2012 08:46
by Lukas
Hello,

i also tried the 6.80.325, but the Exception still occurs.
It's under heavy distributed transaction use and i don't think, that i can reproduce this exception in a simple test.
So if you really need a test project to reproduce the issue, it will probably be a vmware virtual machine or even two of them.
Is this ok for you?

Posted: Thu 29 Mar 2012 12:21
by Shalex
If the issue can not be reproduced with a simple test, send us a complex one.
Also specify the steps we should follow using your test project(s).