Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-11190

JGroups backward compatibility issues

    XMLWordPrintable

Details

    • ER2
    • Hide

      DR18 and DR19 changed how JGroups protocols are configured.

      legacy configuration
      /subsystem=jgroups/stack=tcpping/protocol=TCPPING:add()
/subsystem=jgroups/stack=tcpping/protocol=TCPPING/property=initial_hosts:add(value=192.168.10.1[7600],192.168.10.2[7600])
      configuration change with DR19
      /subsystem=jgroups/stack=tcpping/protocol=TCPPING:add()
/subsystem=jgroups/stack=tcpping/protocol=org.jgroups.protocols.TCPPING/property=initial_hosts:add(value=192.168.10.1[7600],192.168.10.2[7600])
# the old commands do not run

      Affected protocols are at least TCPPING, SYM_ENCRYPT, ASYM_ENCRYPT and with DR19 maybe also AUTH (haven't tried this one yet).

      Additionally, the add-protocol operation no longer works with legacy configuration. Yes, it is deprecated, but if other operations should be backward compatible, this should be as well.

      legacy configuration
      /subsystem="jgroups"/stack="tcpping":add-protocol(type="TCPPING")
# because:
# Operation: /subsystem=jgroups/stack=tcpping:add-protocol(type="TCPPING")
# Failure: WFLYCTL0155: 'socket-bindings' may not be null

      Full sets of commands:
      does not work: http://pastebin.test.redhat.com/488602
      works: http://pastebin.test.redhat.com/488646

      Show
      DR18 and DR19 changed how JGroups protocols are configured. legacy configuration /subsystem=jgroups/stack=tcpping/protocol=TCPPING:add() /subsystem=jgroups/stack=tcpping/protocol=TCPPING/property=initial_hosts:add(value=192.168.10.1[7600],192.168.10.2[7600]) configuration change with DR19 /subsystem=jgroups/stack=tcpping/protocol=TCPPING:add() /subsystem=jgroups/stack=tcpping/protocol=org.jgroups.protocols.TCPPING/property=initial_hosts:add(value=192.168.10.1[7600],192.168.10.2[7600]) # the old commands do not run Affected protocols are at least TCPPING, SYM_ENCRYPT, ASYM_ENCRYPT and with DR19 maybe also AUTH (haven't tried this one yet). Additionally, the add-protocol operation no longer works with legacy configuration. Yes, it is deprecated, but if other operations should be backward compatible, this should be as well. legacy configuration /subsystem="jgroups"/stack="tcpping":add-protocol(type="TCPPING") # because: # Operation: /subsystem=jgroups/stack=tcpping:add-protocol(type="TCPPING") # Failure: WFLYCTL0155: 'socket-bindings' may not be null Full sets of commands: does not work: http://pastebin.test.redhat.com/488602 works: http://pastebin.test.redhat.com/488646

    Description

      QE Cc mnovak1@redhat.com, okalman, mstyk_jira, pkremens
      Cc kkhan1@redhat.com, jgreene@redhat.com

      See steps to reproduce. The question is, to what degree should CLI commands be backward compatible with 7.0? XML configurations pasted from 7.0 are OK in this case.

      I previously thought these changes were OK (once documented in migration guide), but after discussion with the rest of the QE team, the most common opinion is that CLI commands should be 100% backward compatible with 7.0, which is not the case here.

      bozpeyni@redhat.com since this is not stated anywhere I know, can you confirm that CLI commands in 7.1 need to be backward compatible with 7.0?

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11491 JGroups backward compatibility - manipulating the protocol resource needs fully qualified name

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11521 Can not create JGroups TCP stack via ModelNode with enabled assertions

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11492 JGroups backward compatibility - adding AUTH with deprecated operations fails

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-8867 Legacy protocol property resource operations do not work for legacy protocols

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11228 JGroups backward compatibility issues - deprecated add-protocol operation

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11490 Typo in deprecation warning when adding a deprecated property resource on JGroups protocol

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Verified

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              rjanik@redhat.com Richard Janik
              Ondřej Kalman Ondřej Kalman (Inactive)
              Ondřej Kalman Ondřej Kalman (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: