[WFTC-25] update with one recovery call after WFTC is started #24
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ochaloup
force-pushed
the
WFTC-25-one-recovery
branch
from
f062607 to
2b6d750
Compare
|
@dmlloyd : I updated this PR based on our discussion on HipChat. When you have time, please, check the change. Thanks! |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
This is an adjustment of the patch provided for WFTC-25. I think it's not necessary to force running
doRecoverfor each transaction which is not found amongst active ones. It should be enough to load transaction from the object store (by runningrecover) once at the start of the container.From my testing this change should fix the WFTC-25 in the same manner (at least from the https://issues.jboss.org/browse/JBEAP-8635 integration point of view).
https://issues.jboss.org/browse/JBEAP-8635
https://issues.jboss.org/browse/WFTC-25