WFLY-12539 Do not auto-update legacy JGroup protocols in domain contr… #12625
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
wildfly-ci
added
the
deps-ok
bstansberry
approved these changes
Sep 12, 2019
bstansberry
added
the
ready-for-merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
…oller
Wildfly automatically updates legacy JGroup protocols to new versions, e.g. NAKACK to NAKACK2 and UNICAST2 to UNICAST3. However in domain mode we can have Wildfly DC controlling older version (e.g. EAP 6.4) slaves which only know the legacy protocol versions and thus are unable to use the updated versions. To allow for this domain configuration, legacy protocols should not be upgraded by domain controller.
https://issues.jboss.org/browse/WFLY-12539
Downstream issue: https://issues.jboss.org/browse/JBEAP-17511