9 Replies Latest reply on May 16, 2012 2:21 PM by pferraro

    Looking for confirmation about jboss.partition.name

    lindsaybraine

      With reference to JBoss 7.1:

       

      I am trying to understand what has happened to the jboss.partition.name parameter that was present in AS 4,5 and 6.

       

      Posts on various threads around JBoss.org seem to suggest that AS7 no longer needs  jboss.partition.name ? Is this true ?

       

      There is an inference in some posts on this site and others that a 'domain' is effectively a 'partition' - but I am looking into managing separate clusters as a single management domain (becasue I thought that the domain was not the same as a cluster).

       

      The excellant presentation at https://www.jboss.org/dms/AS7/as7webinar/AS7-clustering-webinar.pdf does not shed any light (well, at least not to me ) as to how we would ensure separation of data flow between two clusters run on the same LAN ?

       

      What am I missing / not understanding ?

       

      Any insight would be appreciated.

        • 1. Re: Looking for confirmation about jboss.partition.name
          lindsaybraine

          Clearly I am asking a stupid question - too ridiculous to answer

           

          I am concerned as to whether it is possible to run up two JBoss 7 clusters on the same subnet - and I cant see any mention as to whether this is supported (or not) in the new Infinispan based AS7 world.

           

          Has anyone else tackled this yet ?

          • 2. Re: Looking for confirmation about jboss.partition.name
            pferraro

            The short answer, "jboss.partition.name" isn't used in AS7.  Cluster isolation should be done via unique multicast address/port.

            I realize there's a bit of a terminology gap at work here.  Don't confuse "domain" with "cluster".  A domain is simply a set of servers that are managed together by a single domain controller.  Typically, but not necessarily, a "cluster" will map to a "server group", since a server group is nothing more than a group of servers that share the same configuration, and cluster members typically share server configuration.  A domain can manage multiple server groups, so, yes, you can manage multiple clusters from a single domain controller.

            Let me know if there is still any confusion.

            • 3. Re: Looking for confirmation about jboss.partition.name
              lindsaybraine

              Paul

               

              Many thanks for taking the time - I know you are a busy man.

               

              Your answer was just what I was looking for - crystal clear.

               

              Best Regards

              L

              • 4. Re: Looking for confirmation about jboss.partition.name
                black_dev

                Hi,

                Like Paul Ferraro writed partiotion separated in AS 7 is change multicast address/port ok.

                 

                My question is: change for jgropus* or modcluster ?

                 

                <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
                        <socket-binding name="ajp" port="8009"/>
                        <socket-binding name="http" port="8080"/>
                        <socket-binding name="https" port="8443"/>
                        <socket-binding name="jgroups-diagnostics" port="0" multicast-address="224.0.75.75" multicast-port="7500"/>
                        <socket-binding name="jgroups-mping" port="0" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45700"/>
                        <socket-binding name="jgroups-tcp" port="7600"/>
                        <socket-binding name="jgroups-tcp-fd" port="57600"/>
                        <socket-binding name="jgroups-udp" port="55200" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45688"/>
                        <socket-binding name="jgroups-udp-fd" port="54200"/>
                        <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
                        <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
                        <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>
                        <socket-binding name="modcluster" port="0" multicast-address="224.0.1.106" multicast-port="23366"/>
                        <socket-binding name="osgi-http" interface="management" port="8090"/>
                        <socket-binding name="remoting" port="4447"/>
                        <socket-binding name="txn-recovery-environment" port="4712"/>
                        <socket-binding name="txn-status-manager" port="4713"/>
                        <outbound-socket-binding name="mail-smtp">
                            <remote-destination host="localhost" port="25"/>
                        </outbound-socket-binding>
                    </socket-binding-group>

                please explain more detailed.

                • 5. Re: Looking for confirmation about jboss.partition.name
                  lindsaybraine

                  jgroups would be the one to alter.

                  modcluster is to service northbound web server load balancing etc

                  • 6. Re: Looking for confirmation about jboss.partition.name
                    black_dev

                    Could you give me a example ?

                    • 7. Re: Looking for confirmation about jboss.partition.name
                      black_dev

                      ok, i cooking configurations...

                       

                      jgroups for cluster jboss<>jboss

                       

                      modcluster for httpd<>jboss

                      • 8. Re: Looking for confirmation about jboss.partition.name
                        jkreska

                        I have a followup realted to cluster and multicast address.  In previous versions of jboss if you wanted to lookup an Ejb from a remote client that was in a cluster you didn't set Context.PROVIDER_URL in jndi properties, you set the multicast address and the partitionName.

                         

                        How do you perform a remote client lookup of an EJB running in a cluster without knowing any of the machine names that are in the cluster?