4
Vote

Coupled issue between NMemory and Effort with Transaction

description

The current project that I am on is using the unit of work pattern with the transaction stored in the unit of work.

For some reason during the test, the unit gets created and the transaction started. A save operation is called on an entity, and then I try to read the entity. The save operation happens in a matter of a couple of MS. However, the next operation I have is a read operation where I do a single or default with the saved entities Id, and the operation takes more than 14 seconds. Then when the UOW tries to dispose, the commit fails due to a timedout transaction. Is there any way to extend the timeout for the transaction with NMemory? Is there any reason why a subsequent read would result in a long operation?

file attachments

comments

tamasflamich wrote Apr 22, 2014 at 9:20 PM

Hello,

Thank you for reporting this issue.

May I ask you to provide proof of concept sample code?

RiazThara wrote Nov 24, 2015 at 5:46 PM

I ran into similar issue, and I have attached the code sample herewith showing the test fails (may be not because of timeout, but unable to fetch the recently saved changes), appreciate if you can suggest a solution or point out if there is anything wrong with the usage.