Download packaged distribution from http:\/\/www.jboss.org\/jbossas\/downloads
\nUnpack the compressed archive into a directory of your choice. e.g. \/usr\/jboss<\/p>\n
A cluster is a set of nodes that communicate with each other and work toward a common goal.
\nJBoss currently provides full clustering support. Replication of HTTP sessions for web applications is also available.Can also be integrated to an external balancer.<\/p>\n
- \n
- Scalability (can we handle more users? can we add hardware to our system?)<\/li>\n
- Load Balancing (share the load between servers)<\/li>\n
- High Availability (our application has to be uptime close to 100%)<\/li>\n
- Fault Tolerance (High Availability and Reliability)<\/li>\n
- Clustering support for stateless session beans, stateful session beans, entity beans and JNDI.<\/li>\n<\/ul>\n
<\/p>\n
Partitions<\/strong><\/span><\/div>\nAs previously discussed, a cluster is a set of nodes. In JBoss, a node is a JBoss server instance. Thus, to build a cluster, several JBoss instances have to be grouped in what we call a partition<\/em>.
\nThe partition is the central concept for clustering in JBoss. Partitions are the basic building block of clustering in JBoss.
\nOn a same network, we may have different partitions. In order to differentiate them, each partition must have an individual name.<\/p>\n<\/p>\n
<\/p>\n
<\/div>\nSimple Web Architecture:<\/strong><\/span><\/div>\n<\/p>\n
<\/p>\n
<\/p>\n
Simple web architecture is not scalable. Additional users can only be handled by improving the performance of the server (e.g.adding additional CPUs, more memory). No fault tolerance. If the JBoss AS server goes down, the entire service becomes unavailable.<\/p>\n
<\/div>\nExternal Load Balancer Architecture:<\/span><\/strong>
\nAdd one or many web servers to balance the load to multiple JBoss AS nodes typically running on separate physical servers. Additional user load can be handled by adding another server running JBoss AS. If any one of the JBoss AS nodes fail, the service is still available through other JBoss AS servers.
\n<\/p>\n
A cluster is defined by:<\/strong><\/span><\/p>\n
- \n
- Multicast Address<\/li>\n
- Multicast Post<\/li>\n
- Cluster Name<\/li>\n
- Multicast is the protocol which allow nodes inside to a cluster to communicate without knowing each other. Communication between nodes is provided by JGroups, which is library for multicast communication.<\/li>\n<\/ul>\n
General configuration for the following examples:<\/strong><\/span>
\nPreparing a set of servers to act as a JBoss AS cluster involves a few simple steps:
\nCopy the all directory and create two directory node1 and node2 as below,<\/p>\n<\/p>\n
General configuration for the following examples:<\/strong><\/span>
\nPreparing a set of servers to act as a JBoss AS cluster involves a few simple steps:
\nCopy the all directory and create two directory node1 and node2 as below,<\/p>\n$ cd \/usr\/jboss\/server
\n$ cp -r all jboss1
\n$ cp -r all <\/em>jboss<\/em>2<\/em>
\n$ cp -r all <\/em>jboss3<\/em> <\/em><\/p>\nRequirements Of Jboss Cluster:<\/strong><\/span>
\nCluster Name
\nMulticast Address
\nCluster Name
\nServerPeerID (its unique id for JBoss Messaging.)
\nIn this scenario we have 3 nodes with different ports on same server. Assume the machine has the 192.168.0.101 address assigned. The 3 JBoss instances(jboss1, jboss2 & jboss3) is created under folder \/app\/jboss\/server<\/em> as jboss1, jboss2 & jboss3. The ServerPeerID for the jboss1 is 1, for jboss2 is 2 & for jboss3 is 3. We have decided to set cluster name as “TestPartition” and to use\u00a0239.255.0.10<\/em> as our multicast address.<\/p>\n<\/p>\n
<\/p>\n
Launch a JBoss AS Cluster:<\/strong><\/span><\/p>\n
Now just start JBoss AS cluster nodes one by one as below,
\nFor jboss1<\/span>
\n$JBOSS_HOME\/bin\/run.sh -c jboss1 -b 0.0.0.0 -g TestPartition -u 239.255.0.10 -Djboss.messaging.ServerPeerID=1 -Djboss.service.binding.set=ports-default<\/em><\/p>\nFor jboss2<\/span>
\n$JBOSS_HOME\/bin\/run.sh -c jboss2 -b 0.0.0.0 -g TestPartition -u 239.255.0.10<\/em>
\n-Djboss.messaging.ServerPeerID=2 -Djboss.service.binding.set=ports-02<\/em><\/p>\nFor jboss3<\/span>
\n$JBOSS_HOME\/bin\/run.sh -c jboss3 -b 0.0.0.0 -g TestPartition -u 239.255.0.10<\/em>
\n-Djboss.messaging.ServerPeerID=3 -Djboss.service.binding.set=ports-03<\/em><\/p>\nIn above scripts
\nThe -c<\/em> switch says to use the config \u201c-c node1\u201d.
\nThe -g<\/em> switch sets the cluster name \u201c-u TestPartition\u201d.
\nThe -u<\/em> switch sets the multicast address that will be used for intra-cluster communication
\n\u201c-u 239.255.0.10<\/em>\u201d.
\nThe -b<\/em> switch sets the address on which sockets will be bound \u201c-b 0.0.0.0\u201d.
\nThe -Djboss.messaging.ServerPeerID<\/em> from which JBoss Messaging gets its unique id \u201c-Djboss.messaging.ServerPeerID=1\u201d.
\nThe -Djboss.service.binding.set<\/em> switch sets the port set for instance
\n\u201c-Djboss.service.binding.set=ports-default\u201d.
\nPorts sets are as below.
\nPorts-default = 8080
\nPorts-01 = 8180
\nports-02 = 8280
\nports-03 = 8380<\/p>\nThats it, You have complete your JBoss AS clustering part.<\/p>\n
Load Balancing Using Apache & mod_jk<\/strong><\/span><\/h4>\n
Apache is a well-known web server which can be extended by plugging in modules. One of these modules, mod_jk, has been specifically designed to allow the forwarding of requests from Apache to a Servlet container. Furthermore, it is also able to load-balance HTTP calls to a set of Servlet containers while maintaining sticky sessions.<\/p>\n
\nAdvantages of Fronting with a Web Server :<\/strong><\/span>
\nPerformance: dynamic vs. static content
\nScalability & High Availability: load balancing and fail over
\nSecurity: web servers are simpler and easier to protect
\nStability: proven, more robust
\nFeatures: URL rewriting, fine-grained access control, etc.<\/div>\n<\/div>\nFronting with Apache HTTPD:<\/strong><\/span><\/div>\n\n<\/div>\n
<\/div>\n<\/div>\nSteps for Fronting with Apache HTTPD:<\/strong><\/span>
\nDownload & compile Apache HTTPD
\nDownload & compile mod_jk with Apache
\nAJP Connector on JBoss AS already enabled
\nAccess web apps through Apache
\nMod_jk (version 1.2.x) is the only officially supported connector for Apache+JBoss\/Tomcat
\nintegration.<\/p>\nSteps to install mod_jk<\/strong><\/span>
\nFirst of all, make sure that you have Apache installed. You can download Apache directly from Apache web site at http:\/\/httpd.apache.org. Installation of mod_jk is pretty straightforward and requires no specific configuration. Installation steps are as below,<\/p>\n$tar -zxvf tomcat-connectors-1.2.30-src.tar.gz
\n$cd tomcat-connectors-1.2.30-src\/native
\n$.\/configure –with-apxs=$APACHE_HOME\/bin\/apxs
\n$make
\n$sudo make install<\/em><\/p>\nConfigure Apache to load mod_jk :<\/strong><\/span>
\nInclude configuration file of mod_jk in $APACHE_HOME\/conf\/httpd.conf.
\nAdd below line
\nInclude conf\/mod_jk.conf<\/em><\/p>\nConfiguring mod_jk.conf:<\/strong><\/span>
\nCreate <apache-dir>\/conf\/mod_jk.conf & configure as below.
\n# Load mod_jk module
\nLoadModule jk_module $APACHE_HOME\/modules\/mod_jk.so
\n# Where to find workers.properties
\nJkWorkersFile $APACHE_HOME\/conf\/workers.properties
\n# Where to find mod_jk.log file
\nJkLogFile \/log\/mod_jk.log
\n#Log level
\nJkLogLevel info
\n# Select the log format
\nJkLogStampFormat “[%a %b %d %H:%M:%S %Y]”
\n# JkRequestLogFormat
\nJkRequestLogFormat “%w %V %T”
\n# Add shared memory. This is needed for for load balancing to work properly
\nJkShmFile \/log\/jk.shm
\n# JkOptions indicates to send SSK KEY SIZE
\nJkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
\n# Add jkstatus for managing runtime data
\n<Location \/jkstatus\/>
\nJkMount jkstatus
\nOrder deny,allow
\nDeny from all
\nAllow from {HOST_IP}
\n<\/Location>
\n# Mount your applications
\nJkMountCopy All
\nJkMount \/jmx-console jboss
\nJkMount \/jmx-console\/* jboss
\nJkMount \/admin-console jboss
\nJkMount \/admin-console\/* jboss
\nJkMount \/jkstatus jkstatus<\/p>\nDefine a JBoss AS instance in $APACHE_HOME\/conf\/workers.properties<\/strong><\/span><\/p>\n
worker.list=jboss,jkstatus
\n#For Node1
\nworker.jboss1.type=ajp13
\nworker.jboss1.host=HOST_IP
\nworker.jboss1.port=8009
\nworker.jboss1.lbfactor=1
\n#For Node2
\nworker.jboss2.type=ajp13
\nworker.jboss2.host=HOST_IP
\nworker.jboss2.port=8109
\nworker.jboss2.lbfactor=1
\n#For Node3
\nworker.jboss3.type=ajp13
\nworker.jboss3.host=HOST_IP
\nworker.jboss3.port=8209
\nworker.jboss3.lbfactor=1<\/p>\nworker.jboss.type=lb
\nworker.jkstatus.type=status
\nworker.jboss.sticky_session=1
\nworker.jboss.balance_workers=jboss1,jboss2,jboss3<\/p>\nConfiguring JBoss to work with mod_jk<\/strong><\/span>
\nFinally, we must configure the JBoss AS instances on all clustered nodes so that they can
\nexpect requests forwarded from the mod_jk loadbalancer. On each clustered JBoss node, we have to
\nname the node according to the name specified in workers.properties.<\/p>\n$vim JBOSS_HOME\/server\/jboss1\/deploy\/jbossweb.sar\/server.xml<\/em><\/p>\n
Search for line <Engine name=”jboss.web” defaultHost=”localhost”> & add jvmRoute as below.<\/p>\n
<Engine name=”jboss.web” defaultHost=”localhost” jvmRoute=”jboss1″><\/p>\n
Save & close the file. Make same changes on jboss2 & jboss3.<\/p>\n
You also need to be sure the AJP connector in server.xml is enabled (i.e., uncommented). It is
\nenabled by default. Here your jboss instance is listening on ajp port (8009), you can disable http port
\n(8080).<\/p>\n<!– An AJP 1.3 Connector on port 8009 –>
\n<Connector protocol=”AJP\/1.3″ port=”8009″ address=”${jboss.bind.address}”
\nredirectPort=”8443″ \/><\/p>\nNow restart jboss1, jboss2 & jboss3.
\nAlso restart apache server & check logs.
\nAccess the the url for jmx-console as http:\/\/HOST_IP\/jmx-console & http:\/\/HOST_IP\/jkstatus<\/p>\n","protected":false},"excerpt":{"rendered":"Java Download wget http:\/\/download.oracle.com\/otn-pub\/java\/jdk\/6u33-b04\/jdk-6u33-linux-i586.bin<\/p>\n
Create a bash script to set JAVA_HOME and add Java executables to the path.<\/p>\n
vim \/etc\/profile.d\/java.sh<\/p>\n
export JAVA_HOME=\/opt\/jdk1.6.0_26\/ export PATH=$JAVA_HOME\/bin:$PATH<\/p>\n
5. Source you new script so exports take effect<\/p>\n
source \/etc\/profile.d\/java.sh<\/p>\n
6. Setup Java to be used by the alternatives system (if you want, or if you have an existing install […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18],"tags":[],"_links":{"self":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/825"}],"collection":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=825"}],"version-history":[{"count":1,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/825\/revisions"}],"predecessor-version":[{"id":826,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/825\/revisions\/826"}],"wp:attachment":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=825"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=825"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=825"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}