4 Replies Latest reply on Feb 21, 2012 10:14 AM by Wolf-Dieter Fink

    JBoss 7 Clustering Question

    Joseph Fouts Novice

      Server #1

      Changed standalone-ha.xml  -- Changed IP Address to machine's IP address

       

      <interfaces>

              <interface name="management">

                  <inet-address value="${jboss.bind.address.management:10.100.100.12}"/>

              </interface>

              <interface name="public">

                  <inet-address value="${jboss.bind.address:10.100.100.12}"/>

              </interface>

          </interfaces>

       

      Start server #1

       

      The only message I see in the server log that says anything about a cluster is the following:

       

      14:39:10,267 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015012: Started FileSystemDeploymentService for directory C:\apps\jboss-as-7.1.0.Final\standalone\deployments

      14:39:14,978 INFO  [org.jboss.as.modcluster] (MSC service thread 1-5) JBAS011704: Mod_cluster uses default load balancer provider

      14:39:14,995 INFO  [org.jboss.modcluster.ModClusterService] (MSC service thread 1-5) Initializing mod_cluster 1.2.0.Final

      14:39:15,002 INFO  [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-5) Listening to proxy advertisements on 224.0.1.105:23364

       

       

      Server #2

      Changed standalone-ha.xml  -- Changed IP Address to machine's IP address

       

      <interfaces>

              <interface name="management">

                  <inet-address value="${jboss.bind.address.management:10.100.100.2}"/>

              </interface>

              <interface name="public">

                  <inet-address value="${jboss.bind.address:10.100.100.2}"/>

              </interface>

          </interfaces>

       

      Start server #2

       

      I see the exact log message on the console about the cluster as in server #1.

       

      In jboss 5.1 I would see messages that there were 2 machines now on the cluster.

      How to I verify the cluster in jboss 7?

      Can I check the cosole or CLI?

       

      How do I know that the cluster of the two servers were established?

       

      Also how  do I do a lookup and envocation of a SLSB from another SLSB from within the cluster?  Been looking for this for a few days now.

      Was working in 5.1 now can't seem to figure it out in jboss7.  Not even sure if its even supported yet. 

      I can't seem to get a straight answer. 

      Can someone please help?

       

      Thanks.

        • 1. Re: JBoss 7 Clustering Question
          Wolf-Dieter Fink Master

          In AS7 you don't see any cluster messages until the server deploy a clustered application because the module will not be loaded before.

          See Admin documentation  or the cluster how-to

          • 2. Re: JBoss 7 Clustering Question
            Joseph Fouts Novice

            Deployed same jar with clustered SLSB on both servers.

             

            See both log files below.

             

            Maybe you can see something I don't but the logs show nothing of the two servers forming a cluster.

            Again I had these two machines working with jboss 5.1 so I'm pretty sure as long as jboss 7 did not change anything the multicast should not be a problem.

             

            These logs are not exaclty the same so maybe you or someone else can see something that might be the problem.

             

            Thanks.

             

            ----------------------------------------------------------------------------------------------------------------------------------------------------------

             

             

            Server #1 log

             

            06:10:07,249 INFO  [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service

            06:10:07,251 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]

            06:10:07,256 INFO  [org.jboss.as.security] (MSC service thread 1-6) JBAS013100: Current PicketBox version=4.0.6.final

            06:10:07,457 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) JBoss Web Services - Stack CXF Server 4.0.1.GA

            06:10:07,552 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http--10.100.100.12-8080

            06:10:07,647 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

            06:10:07,647 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 29) JBAS010403: Deploying JDBC-compliant driver class com.ibm.db2.jcc.DB2Driver (version 2.11)

            06:10:07,653 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

            06:10:07,682 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:/admindatasource]

            06:10:07,685 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /10.100.100.12:4447

            06:10:07,685 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory c:\apps\jboss-as-7.1.0.Final\standalone\deployments

            06:10:07,686 INFO  [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on /10.100.100.12:9999

            06:10:12,522 INFO  [org.jboss.as.modcluster] (MSC service thread 1-7) JBAS011704: Mod_cluster uses default load balancer provider

            06:10:17,316 INFO  [org.jboss.modcluster.ModClusterService] (MSC service thread 1-7) Initializing mod_cluster 1.2.0.Final

            06:10:17,324 INFO  [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-7) Listening to proxy advertisements on 224.0.1.105:23364

            06:10:17,353 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "LIDP-ADMI2.jar"

            06:10:17,920 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named TestBean2 in deployment unit deployment "LIDP-ADMI2.jar" are as follows:

             

                java:global/LIDP-ADMI2/TestBean2!com.lidp.main.TestBeanRemoteInf

                java:app/LIDP-ADMI2/TestBean2!com.lidp.main.TestBeanRemoteInf

                java:module/TestBean2!com.lidp.main.TestBeanRemoteInf

                java:jboss/exported/LIDP-ADMI2/TestBean2!com.lidp.main.TestBeanRemoteInf

                java:global/LIDP-ADMI2/TestBean2

                java:app/LIDP-ADMI2/TestBean2

                java:module/TestBean2

             

            06:10:17,923 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named TestBean1 in deployment unit deployment "LIDP-ADMI2.jar" are as follows:

             

                java:global/LIDP-ADMI2/TestBean1!com.lidp.main.TestBeanRemoteInf

                java:app/LIDP-ADMI2/TestBean1!com.lidp.main.TestBeanRemoteInf

                java:module/TestBean1!com.lidp.main.TestBeanRemoteInf

                java:jboss/exported/LIDP-ADMI2/TestBean1!com.lidp.main.TestBeanRemoteInf

                java:global/LIDP-ADMI2/TestBean1

                java:app/LIDP-ADMI2/TestBean1

                java:module/TestBean1

             

            06:10:18,024 INFO  [org.jboss.as] (MSC service thread 1-5) JBAS015874: JBoss AS 7.1.0.Final "Thunder" started in 12016ms - Started 196 of 318 services (120 services are passive or on-demand)

            06:10:18,056 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "LIDP-ADMI2.jar"

            06:11:56,239 INFO  [org.jboss.as.osgi] (MSC service thread 1-2) JBAS011942: Stopping OSGi Framework

             

             

            Server#2 log

             

            06:14:58,890 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 29) JBAS010403: Deploying JDBC-compliant driver class com.ibm.db2.jcc.DB2Driver (version 2.11)

            06:14:58,906 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 28) JBAS016200: Activating ConfigAdmin Subsystem

            06:14:59,015 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 48) JBAS013101: Activating Security Subsystem

            06:14:59,046 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem.

            06:14:59,078 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 42) JBAS011800: Activating Naming Subsystem

            06:14:59,062 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 37) JBAS010260: Activating JGroups subsystem.

            06:14:59,062 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 52) JBAS015537: Activating WebServices Extension

            06:14:59,062 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 43) JBAS011940: Activating OSGi Subsystem

            06:14:59,609 INFO  [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.7.Final)

            06:14:59,625 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.6.final

            06:15:00,015 INFO  [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service

            06:15:00,140 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) JBoss Web Services - Stack CXF Server 4.0.1.GA

            06:15:00,265 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]

            06:15:01,234 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--10.100.100.2-8080

            06:15:01,578 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

            06:15:01,671 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

            06:15:02,156 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory c:\apps\jboss-as-7.1.0.Final\standalone\deployments

            06:15:02,234 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /10.100.100.2:9999

            06:15:02,265 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /10.100.100.2:4447

            06:15:02,390 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:/admindatasource]

            06:15:05,703 INFO  [org.jboss.as.modcluster] (MSC service thread 1-1) JBAS011704: Mod_cluster uses default load balancer provider

            06:15:05,781 INFO  [org.jboss.modcluster.ModClusterService] (MSC service thread 1-1) Initializing mod_cluster 1.2.0.Final

            06:15:05,828 INFO  [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-1) Listening to proxy advertisements on 224.0.1.105:23364

            06:15:05,906 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "LIDP-ADMI2.jar"

            06:15:09,390 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named TestBean2 in deployment unit deployment "LIDP-ADMI2.jar" are as follows:

             

                java:global/LIDP-ADMI2/TestBean2!com.lidp.main.TestBeanRemoteInf

                java:app/LIDP-ADMI2/TestBean2!com.lidp.main.TestBeanRemoteInf

                java:module/TestBean2!com.lidp.main.TestBeanRemoteInf

                java:jboss/exported/LIDP-ADMI2/TestBean2!com.lidp.main.TestBeanRemoteInf

                java:global/LIDP-ADMI2/TestBean2

                java:app/LIDP-ADMI2/TestBean2

                java:module/TestBean2

             

            06:15:09,578 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named TestBean1 in deployment unit deployment "LIDP-ADMI2.jar" are as follows:

             

                java:global/LIDP-ADMI2/TestBean1!com.lidp.main.TestBeanRemoteInf

                java:app/LIDP-ADMI2/TestBean1!com.lidp.main.TestBeanRemoteInf

                java:module/TestBean1!com.lidp.main.TestBeanRemoteInf

                java:jboss/exported/LIDP-ADMI2/TestBean1!com.lidp.main.TestBeanRemoteInf

                java:global/LIDP-ADMI2/TestBean1

                java:app/LIDP-ADMI2/TestBean1

                java:module/TestBean1

             

            06:15:10,000 INFO  [org.jboss.as] (MSC service thread 1-3) JBAS015874: JBoss AS 7.1.0.Final "Thunder" started in 14875ms - Started 196 of 318 services (120 services are passive or on-demand)

            06:15:10,406 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "LIDP-ADMI2.jar"

            06:15:36,609 INFO  [org.jboss.as.osgi] (MSC service thread 1-2) JBAS011942: Stopping OSGi Framework

            06:15:36,640 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Pausing Coyote HTTP/1.1 on http--10.100.100.2-8080

            • 3. Re: JBoss 7 Clustering Question
              Wolf-Dieter Fink Master

              A SLSB does not have a cluster feature, the annotation has no effect at the moment.

              You have to use a clustered SFSB or try the simple web application of the cluster wiki (see link above).

               

              If you deploy the web-app you will see a log message === GMS: === with the cluster information.

              • 4. Re: JBoss 7 Clustering Question
                Wolf-Dieter Fink Master

                As I said continue in one thread, here a link to the same  issue in AS7