Transactional boundary issue for resend #898
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The transactional boundary was incorrectly set (via transactional annotation) at the TransactionManager method level (there was already one at the DAO layer).
In resend method, when recovery needs to be done for large datasets, due to db results pagination,
the resultSet was listed multiple times within this transactional boundary, which results in an increase in memory used that can potentially cause OutOfMemory exception