Friday, June 28, 2013

Oracle SOA


I came across many problems while installing Oracle SOA 11g Version, So I though to write a step by step guide for others ( frankly for me :-) )

The memory Requirements are other essentials can be obtained from the Oracle Web Site.

Here are the necessary Packages that we need to start with ( may require more that 3GB of the Disk Space for the Installation packages) since we are installing in the Windows Xp machine

Oracle Database 10g Express Edition: The SOA Suite requires a Data base for storing data. The Express edition is best choice when we are doing the development. Install OracleXEUniv.exe—recommended for a small footprint database. We will use this for our development Purpose.

Web Logic Server: Oracle SOA best Supported application Server which will provide the JEE environment and also server which will run the SOA suite application ( which is a J2ee application)

Download the “Oracle Web Logic Server 11gR1 (10.3.1) - Package Installer”.
Repository Creation Utility: RCU will help in laying the Data Base Schemas that the SOA Suite Uses for all the Persistence tasks.

SOA Suite: this is the actual JEE application that contains the SOA engines and that will be deployed on WebLogic.

Choose the “SOA Suite, Generic” package, its name is ofm_soa_generic_11.1.1.1.0_disk1_1of1.zip and it is 1.5GB in size.

JDeveloper: IDE that we will use to design and deploy the SOA composites.

Installing the OracleXEUniv

Accept the agreement
Select the Location
Enter the Password ( Omhq126b)
We will see the Screen with details of the Database , Save them
Install Starts.

When you are using XE, you will see a warning when you install the database schema that this database version is too old. You can safely ignore this warning as it applies only to production environments.

When you are using Oracle XE, you must update database parameters if you have never done this for your database installation. You only have to do this once after installing. Set the processes parameter to >=200 using the following instructions.

C:\Documents and Settings\mjagadish>sqlplus system@XE as sysdba

SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jun 19 13:15:02 2013

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Enter password:

Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production

SQL> show parameter session

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
sessions integer 49

SQL> show parameter process

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
processes integer 40

SQL> alter system set sessions=300 scope=spfile;
System altered.


SQL> alter system set processes=300 scope=spfile;
System altered.

Once the Changes are done , restart the oracle XE Service for the changes to get updated.

Installing the Web logic Server.

When the Welcome screen for the install wizard comes up, click on Next.
Skip the email updates and Click next
Select Create a new Middleware Home and enter: D:\Middleware\11GR1\MW_HOME
Select the Typical Install
Review installation directories.
Choose the Default for the Menu Folder
Select “Next” for the Installation Summary
Click on Next to start the installation process. Installation takes about three minutes.

When the installation is complete, deselect the Run Quickstart checkbox and click on Done.

















Repository Creation Utility

Go to the Bin Location of the rcuHome
run the rcu.bat from the Command Prompt

1.In the Welcome Screen , select the Next
2.If we are installing the repository for the first time , we can go with the create option. If we are re installing the Repository then we need to first drop the Schemas and then re create.
Select Create Options ,since we are creating the Database Schemas
3.Enter the Details regarding the Database

















Just Make sure all the above details are correct except the Password.
Click Next

Select Ignore if you see any of the Warnings.
















Once done , click Ok

















In the next screen , select the “SOA and BPM Infrastructure” . A few more will be automatically selected as they are dependencies for the SOA and BPM

Click “next”
The RCU will check the prerequisites

Select the radio button to Use the same password for all schemas. Enter a schema password. Use the same password as we will be needing them later.

in the next screen , select the table space for the components ( use defaults)
Select OK for the warning

Now the RCU creates the table space
In the next screen click the Create to create the Schemas

In the last screen we can see the details like

Once the Repository Creation is done is configured, you can install the SOA server into the Oracle Home on the Web Logic server.

SOA
Select weblogic server By default

1.For Installing the soa , we need to provide the JRE location too. From the DISK1 ( after we unzip the soa ) run the setup using

setup -jreLoc D:\Middleware\11GR1\MW_HOME\jdk160_24

I am here passing the JRE location from the Weblogic Home that we installed earlier.

2.Wait for the pre-requisite check to complete.
3.On the Specify Installation Location screen, select the defaults provided.



















Click on Next.

Review Summary in the next Screen.

Click on Install.

Click on Finish once the Installation is done.

Creating Domain

Once the Installation is done , we need to now configure the SOA domain.

For this ,In a command window, enter:

cd C:\Oracle\Middleware\home_11gR1\Oracle_SOA1\common\bin
exucete “config.cmd”

When the configuration wizard’s Welcome screen comes up, select Create a new WebLogic domain, and then click on Next.

Select Generate a domain and select SOA Suite, Enterprise Manager, and Business Activity Monitoring. Dependent products are selected automatically.

















Click next , and we can see some basic screens as we see in Weblogic Installation. enter the details for them

We will see a Configure JDBC Component Schema screen, you select the components that you want to change, and then enter the property value for those components. First, select all of the components and enter welcome1 for the password in the Schema Password field.

With all of the check boxes selected, enter the Service, Host, and Port values.

















Follow the Next Screens which are similar as installing the Web logic Domain.

Once done start the admin Server from the Newly Creating Domain like

Checking your browser

Oracle SOA Suite 11g has specific browser version requirements.
Enterprise Manager requires Fire fox 3 or IE 7.

BY This the Installation of SOA Suite Is Completed. I will update the Document more with additional details.

Happy learning :-)
Read More

Tuesday, June 25, 2013

JBoss 7 : Data Source Snippets

Create a Data Source
We can Create a data Source using jboss-cli.sh utility available in the JBoss Server like

[standalone@localhost:9999 /] data-source add --name=my_pool --driver-name=mysql --connection-url=jdbc:mysql://localhost:3306/test --jndi-name=java:/mysqlDB --user-name=root --password= --use-ccm=false --max-pool-size=25 –blocking-timeout-wait-millis=5000

Once you create the Data Source we need to enable the pool using

[standalone@localhost:9999 /] data-source enable --name=my_pool

But for this we need to make sure the Drivers are available before creating the Data Source

Creating a Driver

we can create a Driver like

[standalone@localhost:9999 /] /subsystem=datasources/jdbc-driver=mysql:add(driver-name=mysql,driver-module-name=com.mysql)
{"outcome" => "success"}

If we need to delete the driver we can use,

[standalone@localhost:9999 /] /subsystem=datasources/jdbc-driver=mysql:remove
{"outcome" => "success"}

Test the Data Source

If we need to test the Data Source we can use,

[standalone@localhost:9999 /] /subsystem=datasources/data-source=my_pool:test-connection-in-pool
{
"outcome" => "success",
"result" => [true]
}

Read statistics of Data sources
If we need various statistics of the Data Source we can use

/subsystem=datasources/data-source=my_pool/statistics=pool:read-resource(include-runtime=true)

Remove a Data Source
In order to remove a data Source we can use

data-source remove –name=my_pool
Read More

JBoss 7 : Data Source Configuration

Configuring a Data Source in JBoss 7 is different when compared with the JBoss 5 version. In this article we will see how we can configure a Data Source for My Sql Database. Here are the sequences of steps,

1.Configure the Module for the My Sql Data base.
As we are aware that JBoss 7 is based on the modular class loading model. for this we need to create a new module for the my Sql Connector Jars.

Download the My Sql connector jars.
Create a Folder in mysql in /modules/system/layers/base/com and create main directory in mysql like

/modules/system/layers/base/com/mysql/main

Now copy the my Sql jar file to the /modules/system/layers/base/com/mysql/main location.
Once we copied create a file called “module.xml” and add contents

<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="com.mysql">
<resources>
<resource-root path="mysql-connector-java-5.1.25-bin.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
</dependencies>
</module>

This is the module.xml file which tells about the modules to be loaded and also their dependencies. This file exists beside the jar file.

The new module directory should now have the following contents:

module.xml
mysql-connector-java-5.1.17-bin.jar

2.Create a Driver Reference

Now the module has been created, we need to make a reference to it from the main application server configuration file:

cd $JBOSS_HOME/standalone/configuration/
vi standalone-full.xml

Find the ‘drivers’ element and add a new driver to it:

<drivers>
<driver name="mysql" module="com.mysql"/>
<driver name="h2" module="com.h2database.h2">
<xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
</driver>
</drivers>

mySql Driver is now added to the main Configuration File.

3.Create the Datasource
Once the Driver reference is done , the next step is to configure the Data Source.

Go into the configuration directory and open the main configuration file:

cd $JBOSS_HOME/standalone/configuration
vi standalone-full.xml

in the file , find <datasources> element and we can see <datasource> element under this.we can add our data Source like

<datasource jndi-name="java:/mysqlDB" pool-name="my_pool" enabled="true" jta="true" use-java-context="true" use-ccm="true">
<connection-url> jdbc:mysql://localhost:3306/test </connection-url>
<driver> mysql </driver>
<security>
<user-name>root</user-name>
<password> </password>
</security>
<statement>
<prepared-statement-cache-size>
100
</prepared-statement-cache-size>
<share-prepared-statements/>
</statement>
</datasource>

once the Data Source is added. save and re start the Server.

4.Is that Deployed?
We can check the server logs to make sure that the Data Source is bounded. We can see the logs like

15:50:27,058 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:/mysqlDB]

This Clearly says the mySqlDB is bound.

We can see similar message when we un deploy the Data Source like


16:00:41,993 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:/mysqlDB]
Read More

Wednesday, June 19, 2013

A Few JBoss 7 Snippets

Identify the Deployment Location

When the application is deployed , if we need to identify the location where the app is located on file system.

When the deployment is done ,we can see this sort of log at the bottom

14:31:39,759 INFO [org.jboss.as.repository] (HttpManagementService-threads - 4) JBAS014900: Content added at location /soa/jboss-eap-6.1/standalone/data/content/b2/1a30972ac24e7831f1c4c9c831605a60580120/content

Now the content of the deployed app is available at

/soa/jboss-eap-6.1/standalone/data/content/b2/1a30972ac24e7831f1c4c9c831605a60580120

In this location there will be a content directory which have the application contents


Encrypt a Password

To encypt a Password in JBoss 7 we can use

[root@vx111a jboss-eap-6.1]# java -cp $JBOSS_HOME/modules/system/layers/base/org/picketbox/main/picketbox-4.0.17.Final-redhat-1.jar:$JBOSS_HOME/modules/system/layers/base/org/picketbox/main/picketbox-commons-1.0.0.final-redhat-2.jar:$JBOSS_HOME/modules/system/layers/base/org/picketbox/main/picketbox-infinispan-4.0.17.Final-redhat-1.jar:$JBOSS_HOME/modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.0.1.Final-redhat-2.jar org.picketbox.datasource.security.SecureIdentityLoginModule jagadesh

Encoded password: 7b228572f1d62ebcdf8592078de921bc

Remote Deployment Scanner

JBoss allows us to hot deploy a application when we copy the war file in the deployment directory.
The Deployment Scanner scans the deployment location and deploys new wars or any updates done to existing applications.

If we need to disable this , go to /standalone/configuration/standalone.xml file

Remove <extension module="org.jboss.as.deployment-scanner"/> and then remove the:

<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" auto-deploy-zipped="false" auto-deploy-exploded="false"/>
</subsystem>

If you don't want to remove the subsystem, add auto-deploy-zipped="false" and auto-deploy-exploded="false" to the <deployment-scanner/> tag.
If we need to add a external location we can add

<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.0">
<deployment-scanner scan-interval="5000" relative-to="jboss.server.base.dir" path="deployments" />
<deployment-scanner name="my-external-deployment-scanner" path="/home/jpai/as7/deployments" scan-interval="5000" />
</subsystem>


Precompile JSP Pages

We can precompile the jsp page by passing jsp_precompile=true in the parameter. For example if you want to precompile the abc.jsp running on localhost, you have to do http://localhost:80/abc.jsp?jsp_precompile=true this will only precompile the jsp and will not execute it.

JBoss CLI Batch Mode
We can use the batch command available with jboss-cli to perform batch mode commands like

[root@vx111a bin]# ./jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect
[standalone@localhost:9999 /] batch
[standalone@localhost:9999 / #] deploy /root/Downloads/NewFolder/myApp.war
#1 deploy /root/Downloads/NewFolder/myApp.war
[standalone@localhost:9999 / #] run-batch
The batch executed successfully

The commands that are entered after the “batch” command will be executed all at once we run the 'run-batch' command.

Exit the batch edit mode without losing your changes:

[standalone@localhost:9999 / #] holdback-batch
[standalone@localhost:9999 /]
Then activate it later on again:

[standalone@localhost:9999 /] batch
Re-activated batch
#1 deploy /root/Downloads/NewFolder/myApp.war

There are several other notable batch commands available like
clear-batch
edit-batch-line (e.g. edit-batch line 3 create-jms-topic name=mytopic)
remove-batch-line (e.g. remove-batch-line 3)
move-batch-line (e.g. move-batch-line 3 1)
discard-batch

Happy Learning :-)
Read More

Tuesday, June 18, 2013

Cluster Configuration in JBoss 7

The Configuration of Cluster in JBoss 7 is very Easy.

Here are the Sequence of steps to follow to configure a Cluster in JBoss 7
  1. Configure JBoss Servers in Domain Mode. Follow the steps in this link as Usual.
  2. Once you are done with Running JBoss Server in Domain Mode. Now we need to configure another Server on the “Host1” adding that new JBoss Server to “ha-server-group”
  3. Now Configure a new Server in host like
<server name="ha-server-1" group="ha-server-group" auto-start="true">
<socket-bindings port-offset="300"/>
</server>

on the HC side

4.Once you configure these , Start DC using

./domain.sh -b 172.16.101.235 -bmanagement 172.16.101.235

and start the HC Using

./domain.sh -Djboss.domain.master.address=172.16.101.235 -b 172.16.101.196 -bmanagement 172.16.101.196

5.Now from the Management Console , you can see




and also on the Host Screen you can see

















We can see the ha-server-2 configured on host1.

6.The next step is to deploy a application ,

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.

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

on HC Side

[Server:ha-server-2] 18:49:51,515 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 53) JBAS010281: Started repl cache from web container
[Server:ha-server-2] 18:49:51,518 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 54) JBAS010281: Started default-host/ClusterWebApp cache from web container
[Server:ha-server-2] 18:49:51,575 INFO [org.jboss.as.clustering] (MSC service thread 1-3) JBAS010238: Number of cluster members: 2
[Server:ha-server-2] 18:49:51,590 INFO [org.jboss.web] (ServerService Thread Pool -- 53) JBAS018210: Register web context: /ClusterWebApp
[Server:ha-server-2] 18:49:51,851 INFO [org.jboss.as.server] (host-controller-connection-threads - 3) JBAS018559: Deployed "ClusterWebApp.war" (runtime-name : "ClusterWebApp.war")

on DC Side

[Server:ha-server-1] 18:49:50,659 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 53) JBAS010281: Started repl cache from web container
[Server:ha-server-1] 18:49:50,717 INFO [org.jboss.as.clustering] (MSC service thread 1-4) JBAS010238: Number of cluster members: 1
[Server:ha-server-1] 18:49:50,736 INFO [org.jboss.web] (ServerService Thread Pool -- 55) JBAS018210: Register web context: /ClusterWebApp
[Server:ha-server-1] 18:49:50,910 INFO [org.jboss.as.clustering] (Incoming-1,shared=udp) JBAS010225: New cluster view for partition web (id: 1, delta: 1, merge: false) : [masterOne:ha-server-1/web, host1:ha-server-2/web]
[Server:ha-server-1] 18:49:50,913 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,shared=udp) ISPN000094: Received new cluster view: [masterOne:ha-server-1/web|1] [masterOne:ha-server-1/web, host1:ha-server-2/web]
[Server:ha-server-1] 18:49:51,848 INFO [org.jboss.as.server] (host-controller-connection-threads - 3) JBAS018559: Deployed "ClusterWebApp.war" (runtime-name : "ClusterWebApp.war")

We can see the application is deployed in a Clustered Environment. Happy learning :-)
Read More

Monday, June 17, 2013

Running In Domain Mode In JBoss 7

One of the Primary Features of JBoss 7 is the ability to manage multiple JBoss Instances from a Central point. A Collection of Such JBoss servers are said to be members of a Domain which will have a Single Control point for managing the Domain like restarting , applying config changes e.t.c.

In this article we will see how we can run a JBoss Server in a Domain mode.

For the article purpose we will have
2 machine ( 2 IP address)
2 JBoss Servers ( 1 acting as a Domain and other JBoss server running on a Different Host)

Here are the Sequence of steps

1.Unzip the JBoss 7.
2.Make 2 copies of that as “DC” which is a Domain Controller and “HC” as a Host Controller.
3.First Make Changes on the Domain Controller Side

in the DC/Domain/configuration/domain.xml , make the changes as

<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>

We here added a new server Group by the name “ha-server-group”.
4.Next for the hosts.xml file in the DC make changes like

Change the Host Name to

<host name="masterOne" xmlns="urn:jboss:domain:1.4">

Add The Servers

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


5.Once the Changes on the DC side are done , make changes on the HC side like

in the Host.xml , change the Host Name to “host1”

<host name="host1" xmlns="urn:jboss:domain:1.4">

This the host that we manage from the Domain Controller

Now the most important thing is to make changes to the <domain-controller> element.

As we need to communicate with the Domain controller we would have to make sure we replace the “<local/>” tag from the “domain-controller” element in the “host.xml” file, when you are creating a host controller.

The changes to the Domain-controller include

<domain-controller>
<!-- <local/>
<remote host="${jboss.domain.master.address:172.16.101.235}" port="${jboss.domain.master.port:9999}" security-realm="ManagementRealm"/>
</domain-controller>

172.16.101.235 : This is the IP where the Domain System will be running
9999: Port where Domain is running.

Once we are aware of the Domain and where it is running , and also configuring the host and ports in host.xml. We need to now create a secret value and use it in the host configuration file so that domain can perform management operations on the host.

This is used much like a secret key between Domain and Host.

Create a Management User in DC box

[root@vx111a bin]# ./add-user.sh

What type of user do you wish to add?
a) Management User (mgmt-users.properties)
b) Application User (application-users.properties)
(a):

Enter the details of the new user to add.
Realm (ManagementRealm) :
Username : master
Password :
Re-enter Password :
About to add user 'master' for realm 'ManagementRealm'
Is this correct yes/no? yes
Added user 'master' to file '/soa/DC/standalone/configuration/mgmt-users.properties'
Added user 'master' to file '/soa/DC/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="bWFzdGVyMTIzQA==" />

Now copy the Secret value at the bottom to the host.xml file in /DC/hots.xml file

like
<management>
<security-realms>
<security-realm name="ManagementRealm">
<server-identities>
<secret value="aG9zdDEyM0A=" />
</server-identities>
….
.

</management>

The Secret identity is used when a slave domain controller needs to establish a connection to a secured master domain controller.

The value specified for the secret is the password encoded using Base64. On attempting to connect to the remote domain controller the Base64 password will be decoded and the connection will authenticate using the name of the host and the password obtained from the secret. The master domain controller will also need to be configured with a realm that contains the user 'slave' with the specified password.

Once these changes are done. Start the instance using

Start DC using

./domain.sh -b 172.16.101.235 -bmanagement 172.16.101.235

and start the HC Using

./domain.sh -Djboss.domain.master.address=172.16.101.235 -b 172.16.101.196 -bmanagement 172.16.101.196

Once they are started , we can see the logs using

[Host Controller] 17:02:57,178 INFO [org.jboss.as.domain] (slave-request-threads - 1) JBAS010918: Registered remote slave host "host1", JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8)

and we can also see the admin console like















Happy learning :-)
Read More

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 :-)
Read More