-
Notifications
You must be signed in to change notification settings - Fork 3
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
Outcome enlistment handle leak in OletxTransactionManager
#22
Comments
@swh-cb , Is this project still active? We are currently upgrading to .NET 6 and I would like to utilize this library, but was concerned with a potential leak. Is this leak a huge issue, or just something that needs to be cleaned up? |
The issue must be fixed but does not affect productive use of the library. We still use the library in our products targeting .NET 6 without problems. Once .NET 8 is released with long term support (LTS), we will probably switch back to |
@swh-cb , Thanks for responding so quickly. Ok, so sounds like we should be good to use this (I believe). We will be on .NET 6 for the foreseeable future (tied to a 3rd party framework). We are using the latest version of |
@caviyacht Exactly, |
This issue won't be fixed because distributed transactions are supported on Windows starting with .NET 7.0. |
After the transaction has been completed or aborted, the outcome enlistment handle in
OletxTransactionManager
must be released again.The text was updated successfully, but these errors were encountered: