1. Home
  2. Development
  3. Loadbalancing Liferay Portal Servers Bundled with Jboss using F5

Loadbalancing Liferay Portal Servers Bundled with Jboss using F5

Anandababu Bolisetti, modified 10 Years ago.
Loadbalancing Liferay Portal Servers Bundled with Jboss using F5
New Member Posts: 18 Join Date: 1/21/14 Recent Posts
Hello Experts,

We are trying to Load Balance Liferay Portal Servers bundled with Jboss 7.1.1 using F5. When we try reaching the Load Balancer host and port, we are observing a strange behaviour.

If we try to reach https://<<Loadbalancer_Host>>:<<Loadbalancer_Port>>, we are being redirected to https://<<Loadbalancer_Host>>:<<Liferay_Port>>/c/portal/layout page.

We have configured the certificates properly on both the Jboss servers and they are accessible via http/https individually without any issues.

We are not able to identify whether this is issue with the profile we configured on F5 or are we missing the configuration on Jboss.

Regards,
Anand.
thumbnail
David H Nebinger, modified 10 Years ago.
RE: Loadbalancing Liferay Portal Servers Bundled with Jboss using F5
Liferay Legend Posts: 14933 Join Date: 9/2/06 Recent Posts
From the default portal.properties:


#
# Set the HTTP and HTTPs ports when running the portal in a J2EE server that
# is sitting behind another web server like Apache. Set the values to -1 if
# the portal is not running behind another web server like Apache.
#
web.server.http.port=-1
web.server.https.port=-1
Amos Fong, modified 5 Years ago.
RE: Loadbalancing Liferay Portal Servers Bundled with Jboss using F5
Junior Member Posts: 56 Join Date: 5/16/13 Recent Posts
Hi david I am also facing same issue if both liferay node is up in that case I am alwasy rendering welcom page if I am calling sign in page by loadbalncerIP:port/c/portal/login then getting it but after entering username and password it is again rendering me welcome page and I am not able to logged-in.But if  I am putting one node down then  using loadbalncerIP:port I am able to logged-in  on the portal.
Could you suggest what can be the reason of this behaviour where I need to check whether loadbalancer side or our application side?Thanks