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

Broken integration between messaging subsystem and jgroups subsystem

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 9.0.0.Final
    • None
    • Clustering
    • None

      The integration between messaging and jgroups is currently broken. My guess is this was due to recent changes in clustering.

      To reproduce it change the bg-group1 element in standalone-full-ha.xml to replace the socket-binding element with the following:

      	                <jgroups-stack>udp</jgroups-stack>
	                <jgroups-channel>hq-bg</jgroups-channel>
                        <!--<socket-binding>messaging-group</socket-binding>-->

      At boot this appears in the logs:

      10:00:58,707 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
    ("subsystem" => "messaging"),
    ("hornetq-server" => "default")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging.default is missing [jboss.jgroups.stack.udp]"]}
10:00:58,930 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184:    New missing/unsatisfied dependencies:
      service jboss.jgroups.stack.udp (missing) dependents: [service jboss.messaging.default]

      WFLY-3943 is about the lack of testing of this integration,

              pferraro@redhat.com Paul Ferraro
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: