2 Replies Latest reply on Jul 14, 2017 3:31 AM by Kumar Anurag

    Jboss 6.4 clustering in domain mode

    Kumar Anurag Newbie

      Hi all,

       

      I am new to Jboss and wanted to know how to configure clustering on Jboss eap 6.4 which will be running in domain mode.

      Requirement will be as,

      Jboss 6.4 in Domain mode with Clustering.

      2 Servers with 2 instances each i.e. 4 nodes in total.

       

      I tried few configurations but no success so far. Could you please help ?

        • 1. Re: Jboss 6.4 clustering in domain mode
          Abhijit Humbe Master

          Clustering setup is same for standalone and domain mode. You can refer to documentation for more details on clustering. Let us know configuration you have tried and exception you got. You can also go through How to create cluster in JBoss AS 7.1 in domain mode? « JBoss 

          • 2. Re: Jboss 6.4 clustering in domain mode
            Kumar Anurag Newbie

            Tried exactly the same as mentioned in Scenario 2 of the link : How to create cluster in JBoss AS 7.1 in domain mode? « JBoss , except that we used full-ha profile and full-ha sockets. Deployed the application (Dummy.war) using the console, but we ran into below errors in the logs:

             

            ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([

                ("subsystem" => "messaging"),

                ("hornetq-server" => "default")

            ]) - failure description: {

                "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.messaging.default is missing [jboss.binding.messaging-throughput, jboss.binding.messaging]"],

                "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.messaging.default.jms.manager"],

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

                        "jboss.binding.jacorb",

                        "jboss.binding.jacorb-ssl",

                        "jboss.binding.messaging",

                        "jboss.binding.messaging-group",

                        "jboss.binding.messaging-throughput"

                        ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([("subsystem" => "jacorb")]) - failure description: {

            INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015859: Deployed "DummyApp.war" (runtime-name : "DummyApp.war")

            INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

            JBAS014775:    New missing/unsatisfied dependencies:

                  service jboss.binding.jacorb (missing) dependents: [service jboss.jacorb.orb-service]

                  service jboss.binding.jacorb-ssl (missing) dependents: [service jboss.jacorb.orb-service]

                  service jboss.binding.messaging (missing) dependents: [service jboss.messaging.default]

                  service jboss.binding.messaging-group (missing) dependents: [service jboss.messaging.default.bindings.broadcast.bg-group1, service jboss.messaging.default.bindings.discovery.dg-group1]

                  service jboss.binding.messaging-throughput (missing) dependents: [service jboss.messaging.default]

            ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.4.15.GA (AS 7.5.15.Final-redhat-3) started (with errors) in 3670ms - Started 227 of 339 services (10 services failed or missing dependencies, 124 services are lazy, passive or on-demand)