6 Replies Latest reply on Mar 15, 2017 6:51 AM by giacomo.genovese

    Error clustering using a backup node

    giacomo.genovese

      Hi all,

      I'm trying to set up in CapeDwarf a cluster with a live and a backup node(actually in the same machine using two different addresses), as described in Wildfly CookBook, Chapter 13, Messaging with Wildfly-Clustering HornetQ using message replication.

       

      I use to run the live instance first and then the backup one.

      Whatever is the way I deploy my application, using deployments folder, deploying manually first in live node than in backup one and through all the ways to do it I know. I get always error.

      Below the error when I try to deploy application on the backup node:

      12:46:38,694 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "app.war")]) - failure description: {

          "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.deployment.default-server.default-host./app.UndertowDeploymentInfoService is missing [jboss.naming.context.java.JmsXA, jboss.naming.context.java.queue.capedwarf]"],

          "JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {

              "Services that were unable to start:" => [

                  "jboss.capedwarf.warmup.app.default",

                  "jboss.deployment.unit.\"app.war\".deploymentCompleteService",

                  "jboss.undertow.deployment.default-server.default-host./app"

              ],

              "Services that may be the cause:" => [

                  "jboss.naming.context.java.ConnectionFactory",

                  "jboss.naming.context.java.JmsXA",

                  "jboss.naming.context.java.queue.capedwarf"

              ]

          }

      }

      Here the setting of my xml:

      LIVE node

       

      <hornetq-server>

                      <jmx-management-enabled>true</jmx-management-enabled>

                      <cluster-password>${jboss.messaging.cluster.password:XXXX}</cluster-password>

                      <persistence-enabled>true</persistence-enabled>

        <backup>${jboss.messaging.hornetq.backup:false}</backup>

        <failover-on-shutdown>true</failover-on-shutdown>

        <check-for-live-server>true</check-for-live-server>

        <shared-store>false</shared-store>

                      <journal-file-size>102400</journal-file-size>

                      <journal-min-files>2</journal-min-files>

                      <connectors>

      BACKUP node     

          

      <hornetq-server>

                      <persistence-enabled>true</persistence-enabled>

                      <cluster-password>${jboss.messaging.cluster.password:XXXX}</cluster-password>

                      <jmx-management-enabled>true</jmx-management-enabled>

                      <backup>${jboss.messaging.hornetq.backup:true}</backup>

                      <shared-store>false</shared-store>

                      <allow-failback>true</allow-failback>

                      <failover-on-shutdown>true</failover-on-shutdown>

                      <journal-file-size>102400</journal-file-size>

                      <journal-min-files>2</journal-min-files>

       

      Differently, I have no problem using two live nodes in cluster.

       

      Please, Could someone explain why this happens?

       

      Thanks a lot in advance for your help.

       

      Best,

      Giacomo.

        • 1. Re: Error clustering using a backup node
          alesj

          Did you change something in standalone-capedwarf.xml ?

          • 2. Re: Error clustering using a backup node
            giacomo.genovese

            Hi Ales,

             

            I'm using standalone-capedwarf-modules.xml settings a single address for messaging and multicast(jgroups) groups:

            -Djboss.default.multicast.address=230.0.0.4 -Djboss.messaging.group.address=230.0.0.4

            I added only the parameters i showed in the previous message for live and Backup node.

             

            Thanks.

            • 3. Re: Error clustering using a backup node
              alesj

              Unfortunately no idea then.

              As we have cluster tests on CI, and they work as expected.

              • 4. Re: Error clustering using a backup node
                giacomo.genovese

                I notice that, unlike from standalone-full-ha.xml, modcluster is not defined in standalone-capedwarf.xml and standalone-capedwarf-modules.

                the code below is present in standalone-full-ha.xml and missed in standalone-capedwarf.xml

                 

                        <subsystem xmlns="urn:jboss:domain:modcluster:1.2">

                            <mod-cluster-config advertise-socket="modcluster" connector="ajp">

                                <dynamic-load-provider>

                                    <load-metric type="cpu"/>

                                </dynamic-load-provider>

                            </mod-cluster-config>

                        </subsystem>

                Could be this the problem?

                • 5. Re: Error clustering using a backup node
                  ctomc

                  Well, mod cluster is not needed to make cluster work at all.

                   

                  It is optional feature that you can use in combination with apache http for load balancer, so you don't need to statically configure what backend nodes are.

                   

                  see mod_cluster - JBoss Community  for more details

                  • 6. Re: Error clustering using a backup node
                    giacomo.genovese

                    Hi Tomaz,

                     

                    Thanks, I wrote about mod-cluster because it is the major difference I notice in the xml configuration file.

                    I knew about its feature on load balancing.

                     

                    Do you think that the problem could be related to the GAE application I'm using?

                     

                    Thanks.