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

TransactionScopeManager: resources registered while a transaction is already active are not enlisted #4

SummerBatchTeam opened this Issue Jul 1, 2016 · 0 comments


None yet
1 participant

SummerBatchTeam commented Jul 1, 2016

The transaction scope manager allows registering resources to automatically enlist them when a transaction is opened, but if a transaction is already active the resource is not enlisted in it.

This is an issue with transactional writers that will wait a commit confirmation that they will possibly never receive.

@SummerBatchTeam SummerBatchTeam added the bug label Jul 1, 2016

@SummerBatchTeam SummerBatchTeam self-assigned this Jul 1, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment