Skip to main content

Load Balancing and Clustering Liferay

There are two ways of Clustering Liferay on Tomcat
1. Sticky Session
User request will always goes to same Liferay instance
2. Session Replication
User request can go to any tomcat in cluster and his session is copied on entire cluster


Lets get started for Sticky Session based clustering and load balancing.

Use-Case
Setting up two tomcat Liferay along with apache on same windows machine.

Pre-requirements
1. install Apche 2.x
2. download Liferay5.x and make an extra copy

Steps 1. open httpd.conf from apache_home/conf/ and add these lines at the end

<Proxy balancer://mycluster>
BalancerMember ajp://localhost:8009/ route=tomcatA smax=15 max=50 loadfactor=20
BalancerMember ajp://localhost:8010/ route=tomcatB smax=15 max=50 loadfactor=20
</Proxy>

<Location / >
ProxyPass balancer://mycluster/ stickysession=JSESSIONID
</Location>

<Location /balancer-manager>
SetHandler balancer-manager
Order Deny,Allow
Deny from all
Allow from localhost
</Location>

Step 2.

uncomment the following four lines on httpd.conf

LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule status_module modules/mod_status.so

Step 3.

open liferay/tomcat_home_1/conf/server.xml and add jvmRoute="tomcatA" to the following line

Engine name="Catalina" defaultHost="localhost"

so it should look like this
Engine name="Catalina" defaultHost="localhost" jvmRoute="tomcatA"

Step 4.

open liferay/tomcat_home_2/conf/server.xml and add jvmRoute="tomcatB" to the following line

Engine name="Catalina" defaultHost="localhost"

so it should look like this
Engine name="Catalina" defaultHost="localhost" jvmRoute="tomcatB

also change the following port nos


Server port="8006" shutdown="SHUTDOWN"

Connector port="8081" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8444"

Connector port="8010" protocol="AJP/1.3" redirectPort="8444"

Thats It!

start apache, tomcatA, tomcatB and

navigate to http://localhost/
also checkout balancer-manager

for more configuration and understanding checkout the following link



If your tomcats run on different server make sure you change index directory to some central place (e.g /common-dir/liferay ) i.e resource.repositories.root=/common-dir/liferay in portal-ext.properties


Comments

Anonymous said…
This comment has been removed by a blog administrator.
Anonymous said…
In a fantastic way!
joseph said…
Dear Intesar,

thanks for well documentated steps..

it;s a great help to us.

Appreciate if you can touch up on session replication instead of sticky session?
Anonymous said…
Peccato che non hai l'allineamento dei dati :)

Popular posts from this blog

Access multiple Databases in JPA

According to JPA specification we can define multiple "persistence-unit" elements (i.e. like below) in persistence.xml file and can easily refer them inside Dao layers as this. public class PolarDaoImpl {     @PersistenceContext(unitName="PolarPU")     protected EntityManager entityManager; -- } public class BearDaoImpl {     @PersistenceContext(unitName="BearPU")     protected EntityManager entityManager; -- } Checkout sample persistence.xml <?xml version="1.0" encoding="UTF-8"?> <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">     <!-- Database 1 -->     <persistence-unit name="PolarPU" transaction-type="RESOURCE_LOCAL">         <

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax. Example 1: Stores list of Strings in an Entity @Entity public class Users implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ElementCollection     private List<String> certifications = new ArrayList <String> ();     public Long getId() {         return id;     }     public void setId(Long id) {         this.id = id;     }     public List <String> getCertifications() {         return certifications;     }     public void setCertifications(List <String> certifications) {         this.certifications = certifications;     } .. }         Users u = new Users();         u.getCertifications().add("Sun Certified Java Programmer");         em.persist(u); Generated Tables    Users    Co

Reuse JPA Entities as DTO

Note : Major design advantages of JPA Entities are they can detached and used across tiers and networks and later can by merged. Checkout this new way of querying entities in JPA 2.0 String ql = " SELECT new prepclass2.Employee (e.firstname, e.lastname) FROM Employee e "; List<Employee> dtos = em.createQuery(ql).getResultList(); The above query loads all Employee entities but with subset of data i.e. firstname, lastname. Employee entity looks like this. @Entity @Table(name="emp") public class Employee implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @Column     private String firstname;     @Column     private String lastname;     @Column     private String username;     @Column     private String street;     @Column     private String city;     @Column     private String state;     @Column     private String zipc