-
Notifications
You must be signed in to change notification settings - Fork 930
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using DependentTransaction fails #2172
Comments
There is some ongoing work to support dependent transaction in NH 5.x, currently targeted to 5.2.x but which may be back-ported down to 5.0.x. See #2197. Since this regression is two years old and is only reported now, it seems using dependent transaction is not very common place. And we were indeed not having any test on them. Just fixing the test case you provide here may not be enough to fix it entirely. To avoid a multi-releases fix process, may you please test the binaries from the PR builds with your real case application? In the PR's builds list, you can go to the details of "NHibernate (Release Package)" build, login into TeamCity (anonymous logon available), and retrieves build artifacts (including a NuGet package) from the artifacts tab. |
Fix nhibernate#2172 in 5.1.x
Fix nhibernate#2172 in 5.0.x
Ok ,thanks very much |
When I use
Transaction.Current.DependentClone(DependentCloneOption.RollbackIfNotComplete)
, Nhibernate went wrong. The error message isHibernateException: Synchronization timeout for transaction completion. Either raise {Cfg.Environment.SystemTransactionCompletionLockTimeout}, or this may be a bug in NHibernate.
. This error may occur in NHibernate 5.x.xHere is the code:
The text was updated successfully, but these errors were encountered: