Tuesday, June 11, 2013

JBoss 7 Clustering : Domain Mode Clustering With Single IP address

In this article we will see how to configure JBoss 7 Cluster in the Domain Mode on a Single IP address.

1.Configure a New Server Group in the /domain/configuration/domain.xml file like

<server-group name="ha-server-group" profile="ha">
<jvm name="default">
<heap size="256m" max-size="256m"/>
<permgen max-size="128m"/>
</jvm>
<socket-binding-group ref="ha-sockets"/>
</server-group>

Now we have a Server group by Name “ha-server-group” which is a “ha” profile. The default configuration includes four preconfigured profiles:

default - Support of Java EE Web-Profile plus some extensions like RESTFul Web Services or support for EJB3 remote invocations
full - Support of Java EE Full-Profile and all server capabilities without clustering
ha - default profile with clustering capabilities
full-ha - full profile with clustering capabilities

we use the “ha” profile here.

2.Now Configure the Servers in /domain/configuration/hosts.xml file like

<server name="ha-server-1" group="ha-server-group" auto-start="true">
<socket-bindings port-offset="300"/>
</server>

<server name="ha-server-2" group="ha-server-group" auto-start="true">
<socket-bindings port-offset="400"/>
</server>

We configured 2 server by the names “ha-server-1” and “ha-server-2”.The Socket Bindings are different for these.

3.Once we configure the servers and Server groups ,we need to create a User for the management tasks.use the ./add-user.sh script for creating the users


Enter the details of the new user to add.
Realm (ManagementRealm) :
Username : adminuser
Password :

Username (adminuser) : adminuser
Password :
Re-enter Password :
About to add user 'adminuser' for realm 'ManagementRealm'
Is this correct yes/no? yes
Added user 'adminuser' to file '/soa/jboss-eap-6.1/standalone/configuration/mgmt-users.properties'
Added user 'adminuser' to file '/soa/jboss-eap-6.1/domain/configuration/mgmt-users.properties'
Is this new user going to be used for one AS process to connect to another AS process?
e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server EJB calls.
yes/no? yes
To represent the user add the following to the server-identities definition <secret value="amJzNDEyM0A=" />


4.Now start the Domain using
[root@vx111a bin]# ./domain.sh
============================================================

JBoss Bootstrap Environment

JBOSS_HOME: /soa/copy-eap6

JAVA: /usr/jdk1.6.0_14/bin/java

JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

15:48:37,099 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
15:48:37,186 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
[Host Controller] 15:48:37,664 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
[Host Controller] 15:48:37,791 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
[Host Controller] 15:48:37,856 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
[Host Controller] 15:48:38,336 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.7.GA-redhat-1
[Host Controller] 15:48:38,340 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
[Host Controller] 15:48:38,343 INFO [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (management) port (9990) securePort (-1)
[Host Controller] 15:48:38,347 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.16.GA-redhat-1

[Server:ha-server-1] 15:48:51,983

INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 44) JBAS010260: Activating JGroups subsystem.
[Server:ha-server-1] 15:48:51,992 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 51) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
[Server:ha-server-1] 15:48:51,986 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) JBAS010280: Activating Infinispan subsystem.
[Server:ha-server-1] 15:48:52,001 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
[Server:ha-server-1] 15:48:52,010 INFO [org.jboss.as.security] (ServerService Thread Pool -- 33) JBAS013171: Activating Security Subsystem
[Server:ha-server-1] 15:48:52,170 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 52) JBAS016200: Activating ConfigAdmin Subsystem
[Server:ha-server-1] 15:48:52,177 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 29) JBAS015537: Activating WebServices Extension
[Server:ha-server-1] 15:48:52,185 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 41) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
[Server:ha-server-2] 15:48:52,308 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
[Server:ha-server-1] 15:48:52,873 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
[Server:ha-server-1] 15:48:52,874 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.17.Final-redhat-1
[Server:ha-server-1] 15:48:53,070 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.17.Final-redhat-1)
[Server:ha-server-1] 15:48:53,375 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
[Server:ha-server-1] 15:48:53,395 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 48) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-1] 15:48:53,400 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 48) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-2] 15:48:53,457 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
[Server:ha-server-1] 15:48:53,565 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.3.Final-redhat-3
[Server:ha-server-2] 15:48:53,662 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
[Server:ha-server-2] 15:48:53,869 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.7.GA-redhat-1
[Server:ha-server-2] 15:48:53,877 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
[Server:ha-server-2] 15:48:53,885 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.16.GA-redhat-1
[Server:ha-server-1] 15:48:53,984 INFO [org.apache.coyote.ajp] (MSC service thread 1-1) JBWEB003046: Starting Coyote AJP/1.3 on ajp-/127.0.0.1:8309
[Server:ha-server-1] 15:48:53,985 INFO [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/127.0.0.1:8380
[Server:ha-server-1] 15:48:53,989 INFO [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003000: Coyote HTTP/1.1 starting on: http-/127.0.0.1:8380
[Server:ha-server-1] 15:48:54,096 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:4747
[Server:ha-server-1] 15:48:54,125 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 7) MODCLUSTER000001: Initializing mod_cluster ${project.version}
[Server:ha-server-1] 15:48:54,237 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
[Server:ha-server-1] 15:48:54,239 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 7) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
[Server:ha-server-1] 15:48:54,317 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) started in 7848ms - Started 122 of 232 services (109 services are passive or on-demand)
[Host Controller] 15:48:54,884 INFO [org.jboss.as.domain.controller.mgmt] (Remoting "vx111a.example.com:MANAGEMENT" task-3) JBAS010920: Server [Server:ha-server-2] registered using connection [Channel ID 29aa89c5 (inbound) of Remoting connection 00625c49 to /127.0.0.1:30049]
[Host Controller] 15:48:55,066 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
[Host Controller] 15:48:55,067 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
[Host Controller] 15:48:55,067 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) (Host Controller) started in 17818ms - Started 11 of 11 services (0 services are passive or on-demand)
[Host Controller] 15:48:55,076 INFO [org.jboss.as.host.controller] (server-registration-threads - 1) JBAS010919: Registering server ha-server-2
[Server:ha-server-2] 15:48:55,876 INFO [org.jboss.as.security] (ServerService Thread Pool -- 32) JBAS013171: Activating Security Subsystem
[Server:ha-server-2] 15:48:55,878 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800: Activating Naming Subsystem
[Server:ha-server-2] 15:48:55,882 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 40) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
[Server:ha-server-2] 15:48:55,888 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 43) JBAS010260: Activating JGroups subsystem.
[Server:ha-server-2] 15:48:55,889 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 28) JBAS015537: Activating WebServices Extension
[Server:ha-server-2] 15:48:55,893 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 47) JBAS010280: Activating Infinispan subsystem.
[Server:ha-server-2] 15:48:55,912 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 51) JBAS016200: Activating ConfigAdmin Subsystem
[Server:ha-server-2] 15:48:55,943 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 50) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
[Server:ha-server-2] 15:48:56,240 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current PicketBox version=4.0.17.Final-redhat-1
[Server:ha-server-2] 15:48:56,489 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.17.Final-redhat-1)
[Server:ha-server-2] 15:48:56,640 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
[Server:ha-server-2] 15:48:56,703 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
[Server:ha-server-2] 15:48:56,960 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.3.Final-redhat-3
[Server:ha-server-2] 15:48:57,109 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 47) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-2] 15:48:57,114 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 47) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-2] 15:48:57,150 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/127.0.0.1:8480
[Server:ha-server-2] 15:48:57,182 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003000: Coyote HTTP/1.1 starting on: http-/127.0.0.1:8480
[Server:ha-server-2] 15:48:57,208 INFO [org.apache.coyote.ajp] (MSC service thread 1-4) JBWEB003046: Starting Coyote AJP/1.3 on ajp-/127.0.0.1:8409
[Server:ha-server-2] 15:48:57,308 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 52) MODCLUSTER000001: Initializing mod_cluster ${project.version}
[Server:ha-server-2] 15:48:57,325 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 52) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
[Server:ha-server-2] 15:48:57,424 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
[Server:ha-server-2] 15:48:57,428 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:4847
[Server:ha-server-2] 15:48:57,476 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) started in 6360ms - Started 122 of 232 services (109 services are passive or on-demand)

You can see at the end of the logs ,that both the server “ha-server-1” and “ha-server-2” were started.

5.Now open the Management Console and we can see there are 3 tabs , in the run time tab we can see the Server group “ha-server-group” and the servers “ha-server-1” and “ha-server-2” associated with the group.

 
We can also see that both the servers are started.

6.Now if you check the hosts tab, we can see both the servers. The details including the Port configurations can be seen below.


 7.In order to make the cluster work , we need to deploy an application which has the <distributable/> tag available in the applications web.xml file.

Deploy the application like


Click On the “Manage Deployments” on the Right side
Click On the “Add” on the Left Side
Browse the File and select Ok for deployment.
Once the application is deployed , we need to enable the application.

8.Once the application is enabled , we need to assign it the server-group like

















Select the Server-group(ha-Server-group).Select the Group Deployment.
The above screen will appear. Select the “assign” button to select the application.
Select the application and click Assign to assign the application to the Server -group.
Once it is assigned , enable the application on the server-group. At this point you can see the logs filling like

[Server:ha-server-2] 15:50:25,323 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "myApp.war" (runtime-name: "myApp.war")
[Server:ha-server-1] 15:50:25,359 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "myApp.war" (runtime-name: "myApp.war")
[Server:ha-server-2] 15:50:26,474 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation
configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-2] 15:50:26,474 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-2] 15:50:26,479 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-2] 15:50:26,479 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-2] 15:50:26,479 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-2] 15:50:26,498 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-2] 15:50:26,530 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 56) ISPN000078: Starting JGroups Channel
[Server:ha-server-2] 15:50:26,548 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 56) [JGRP00014] the receive buffer of socket DatagramSocket was set to 20MB, but the OS only allocated 4.19MB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
[Server:ha-server-2] 15:50:26,549 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 56) [JGRP00014] the receive buffer of socket MulticastSocket was set to 25MB, but the OS only allocated 4.19MB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
[Server:ha-server-2] 15:50:26,551 INFO [stdout] (ServerService Thread Pool -- 56)
[Server:ha-server-2] 15:50:26,551 INFO [stdout] (ServerService Thread Pool -- 56) -------------------------------------------------------------------
[Server:ha-server-2] 15:50:26,552 INFO [stdout] (ServerService Thread Pool -- 56) GMS: address=master:ha-server-2/web, cluster=web, physical address=127.0.0.1:55600
[Server:ha-server-2] 15:50:26,552 INFO [stdout] (ServerService Thread Pool -- 56) -------------------------------------------------------------------
[Server:ha-server-1] 15:50:26,930 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-1] 15:50:26,929 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-1] 15:50:26,933 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-1] 15:50:26,933 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-1] 15:50:26,934 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-1] 15:50:26,934 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[Server:ha-server-1] 15:50:26,991 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 54) ISPN000078: Starting JGroups Channel
[Server:ha-server-1] 15:50:27,004 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 54) [JGRP00014] the receive buffer of socket DatagramSocket was set to 20MB, but the OS only allocated 4.19MB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
[Server:ha-server-1] 15:50:27,004 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 54) [JGRP00014] the receive buffer of socket MulticastSocket was set to 25MB, but the OS only allocated 4.19MB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
[Server:ha-server-1] 15:50:27,006 INFO [stdout] (ServerService Thread Pool -- 54)
[Server:ha-server-1] 15:50:27,006 INFO [stdout] (ServerService Thread Pool -- 54) -------------------------------------------------------------------
[Server:ha-server-1] 15:50:27,007 INFO [stdout] (ServerService Thread Pool -- 54) GMS: address=master:ha-server-1/web, cluster=web, physical address=127.0.0.1:55500
[Server:ha-server-1] 15:50:27,007 INFO [stdout] (ServerService Thread Pool -- 54) -------------------------------------------------------------------
[Server:ha-server-1] 15:50:29,044 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 54) ISPN000094: Received new cluster view: [master:ha-server-1/web|0] [master:ha-server-1/web]
[Server:ha-server-1] 15:50:29,153 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 54) ISPN000079: Cache local address is master:ha-server-1/web, physical addresses are [127.0.0.1:55500]
[Server:ha-server-1] 15:50:29,158 INFO [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 54) ISPN000128: Infinispan version: Infinispan 'Delirium' 5.2.6.Final
[Server:ha-server-1] 15:50:29,198 INFO [org.infinispan.factories.TransactionManagerFactory] (ServerService Thread Pool -- 58) ISPN000161: Using a batchMode transaction manager
[Server:ha-server-1] 15:50:29,201 INFO [org.infinispan.factories.TransactionManagerFactory] (ServerService Thread Pool -- 54) ISPN000161: Using a batchMode transaction manager
[Server:ha-server-1] 15:50:29,221 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,shared=udp) ISPN000094: Received new cluster view: [master:ha-server-1/web|1] [master:ha-server-1/web, master:ha-server-2/web]
[Server:ha-server-2] 15:50:29,254 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 56) ISPN000094: Received new cluster view: [master:ha-server-1/web|1] [master:ha-server-1/web, master:ha-server-2/web]
[Server:ha-server-1] 15:50:29,389 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 58) ISPN000031: MBeans were successfully registered to the platform MBean server.
[Server:ha-server-1] 15:50:29,398 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 58) JBAS010281: Started default-host/myApp cache from web container
[Server:ha-server-1] 15:50:29,422 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 54) ISPN000031: MBeans were successfully registered to the platform MBean server.
[Server:ha-server-1] 15:50:29,425 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 54) JBAS010281: Started repl cache from web container
[Server:ha-server-1] 15:50:29,434 INFO [org.jboss.as.clustering] (MSC service thread 1-2) JBAS010238: Number of cluster members: 2
[Server:ha-server-1] 15:50:29,455 INFO [org.jboss.web] (ServerService Thread Pool -- 58) JBAS018210: Register web context: /myApp
[Server:ha-server-2] 15:50:29,368 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 56) ISPN000079: Cache local address is master:ha-server-2/web, physical addresses are [127.0.0.1:55600]
[Server:ha-server-2] 15:50:29,384 INFO [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 56) ISPN000128: Infinispan version: Infinispan 'Delirium' 5.2.6.Final
[Server:ha-server-2] 15:50:29,475 INFO [org.infinispan.factories.TransactionManagerFactory] (ServerService Thread Pool -- 56) ISPN000161: Using a batchMode transaction manager
[Server:ha-server-2] 15:50:29,566 INFO [org.infinispan.factories.TransactionManagerFactory] (ServerService Thread Pool -- 53) ISPN000161: Using a batchMode transaction manager
[Server:ha-server-2] 15:50:29,655 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 53) ISPN000031: MBeans were successfully registered to the platform MBean server.
[Server:ha-server-2] 15:50:29,661 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 56) ISPN000031: MBeans were successfully registered to the platform MBean server.
[Server:ha-server-2] 15:50:29,749 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 53) JBAS010281: Started repl cache from web container
[Server:ha-server-2] 15:50:29,754 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 56) JBAS010281: Started default-host/myApp cache from web container
[Server:ha-server-2] 15:50:29,763 INFO [org.jboss.as.clustering] (MSC service thread 1-4) JBAS010238: Number of cluster members: 2
[Server:ha-server-2]
15:50:29,773 INFO [org.jboss.web] (ServerService Thread Pool -- 53) JBAS018210: Register web context: /myApp
[Server:ha-server-2] 15:50:29,938 INFO [org.jboss.as.server] (host-controller-connection-threads - 2) JBAS018559: Deployed "myApp.war" (runtime-name : "myApp.war")
[Server:ha-server-1] 15:50:29,939 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "myApp.war" (runtime-name : "myApp.war")



Happy learning :-)