Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-9854

jgroups-channel cannot use name which is already used by jgroups/stacks

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Blocker
    • 12.0.0.Final
    • 12.0.0.Beta1
    • Clustering, JMS
    • None
    • Hide

      Run following CLI command with standalone-full-ha profile.

      /subsystem=messaging-activemq/server=default/broadcast-group=bg-group2:add(jgroups-stack=udp,jgroups-channel=udp)
      Show
      Run following CLI command with standalone-full-ha profile. /subsystem=messaging-activemq/server= default /broadcast-group=bg-group2:add(jgroups-stack=udp,jgroups-channel=udp)
    • Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration

    Description

      The configuration [1] results to an error [2]. This is backward compatibility issue since the configuration works with previous releases of Wildfly.

      [1]

      <broadcast-group name="bg-group1" jgroups-stack="udp" jgroups-channel="udp" broadcast-period="2000" connectors="connector"/>

      [2]

      10:52:29,982 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 15) WFLYCTL0013: Operation ("add") failed - address: ([
    ("subsystem" => "jgroups"),
    ("channel" => "udp")
]) - failure description: "WFLYCTL0436: Cannot register capability 'org.wildfly.clustering.jgroups.channel-factory.udp' at location '[
    (\"subsystem\" => \"jgroups\"),
    (\"channel\" => \"udp\")
]' as it is already registered in context 'global' at location(s) '[[
    (\"subsystem\" => \"jgroups\"),
    (\"stack\" => \"udp\")
]]'"

      Attachments

        Issue Links

          is documented by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-14529 jgroups-channel cannot use name which is already used by jgroups/stacks

          • 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-14164 Server does not start with Artemis configured using JGroups TCP stack

          • 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

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              eduda_jira Erich Duda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: