This question is locked. New answers and comments are not allowed.
Sometimes I see an error message that a transaction is already closed (for long running transactions in which a lot of objects are changed).
My first reaction was to monitor all the Commits (no rollback is done), but in this case no Commit seems to be done. (old object model)
Is there anything else which could be monitored to get informed that a connection is closed?
My first reaction was to monitor all the Commits (no rollback is done), but in this case no Commit seems to be done. (old object model)
Is there anything else which could be monitored to get informed that a connection is closed?
4 Answers, 1 is accepted
0
Hi Wolfgang,
You say that there are no commits done yet and still there is a transaction running. Are you flushing the changes periodically in between? If you Flush (scope.Transaction.Flush) then there is an active transaction which is not committed until you call Commit.
Regards,
Ady
Telerik
You say that there are no commits done yet and still there is a transaction running. Are you flushing the changes periodically in between? If you Flush (scope.Transaction.Flush) then there is an active transaction which is not committed until you call Commit.
Regards,
Ady
Telerik
OpenAccess ORM Q3 2013 simplifies your model operations even further providing you with greater flexibility. Check out the list of new features shipped with our latest release!
0
Wolfgang
Top achievements
Rank 1
Rank 1
answered on 06 Dec 2013, 10:03 AM
No, i do not flush something explicitly.
0
Hello Wolfgang,
Do you have any more information about the error - the call stack or code that is causing the exception?
It seems that some action has caused a transaction to be started and I need to know what code could have possible caused the error.
Regards,
Ady
Telerik
Do you have any more information about the error - the call stack or code that is causing the exception?
It seems that some action has caused a transaction to be started and I need to know what code could have possible caused the error.
Regards,
Ady
Telerik
OpenAccess ORM Q3 2013 simplifies your model operations even further providing you with greater flexibility. Check out the list of new features shipped with our latest release!
0
Wolfgang
Top achievements
Rank 1
Rank 1
answered on 11 Dec 2013, 07:19 AM
Hi Ady,
no. as we also had the other error that with large commits sometimes the order of created object does not seems to be right (a foreign key was then missing) I changed the code to commit after every created object (which makes the runtime a lot slower...). Since then also this error did not appear.
Best regards,
Wolfgang
no. as we also had the other error that with large commits sometimes the order of created object does not seems to be right (a foreign key was then missing) I changed the code to commit after every created object (which makes the runtime a lot slower...). Since then also this error did not appear.
Best regards,
Wolfgang