Our application process thousands of "workflow steps" daily. We get the random and not reproducible error "System.NullReferenceException: Object reference not set to an instance of an object." on the SubmitChages. This happens just after deleting an object from the database. The "funny" thing is that in 100% percent of the cases retrying the exact same code afterwards works. Below follows the last command executed and the callstack of the error. We are using Devart version 8.5.464.
I've looked in your forum and it seems that there are some entries regarding Null Exception on SubmitChanges but none of them with such a call stack.
Code: Select all
DELETE FROM PUMA_WORKFLOW_INSTANCE WHERE ID = :key1 -- key1: Input Number (Size = 0; DbType = Decimal)  -- Context: Devart.Data.Oracle.Linq.Provider.OracleDataProvider Mapping: AttributeMappingSource Build: 4.5.802.0 2017-01-31 17:25:52,678 ERROR Exception caught on WorkflowEnd: Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at xget__Id_955(Workflow ) at Devart.Data.Linq.Mapping.Accessors.d.Accessor`2.GetValue(T instance) at Devart.Data.Linq.Mapping.Accessors.MetaAccessor`2.GetBoxedValue(Object instance) at Devart.Data.Linq.Engine.b2.c.c() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at Devart.Data.Linq.Engine.c4.i(IObjectEntry A_0) at Devart.Data.Linq.Engine.c4.l() at Devart.Data.Linq.Engine.c4.j() at Devart.Data.Linq.Engine.b3.a(ConflictMode A_0) at Devart.Data.Linq.DataContext.SubmitChanges(ConflictMode failureMode) (...)