Service Updates for Liferay Cloud Version 3 and 4

The services update to 2020.30.1 includes updates to the database, liferay, and webserver services.

Version Compatibility between 3 and 4

For details on service compatibility between version 3 and 4 please see release update 6/11/2020 Services Update 2020.24.1 or 5/28/2020 Services Update 2020. 22.1 

Webserver and Liferay Service Timeout Settings

New environment variables have been added that allow users to configure timeout settings on both the webserver and liferay services. Configuring these timeouts may be necessary for use cases that involve uploading of large files to Liferay (e.g. importing large lar files).

Webserver (Nginx and HAProxy)

There are two environment variables that can be modified to control timeouts on both Nginx and HAProxy. The new environment variables as well as the properties that are affected for each respective server can be found below. Note that the values for each can be described in various time units, including milliseconds (ms), seconds (s), minutes (m), and hours (h).

Environment Variable	Default Value	Properties Affected
LCP_WEBSERVER_GLOBAL_TIMEOUT	60s	fastcgi_read_timeout uwsgi_read_timeout uwsgi_send_timeout uwsgi_send_timeout proxy_connect_timeout proxy_read_timeout proxy_send_timeout
LCP_HAPROXY_GLOBAL_TIMEOUT	10m	client server tunnel http-request http-keep-alive client-fin server-fin

 

Liferay (Tomcat)

There are two ways that one can configure Tomcat's session timeout without modifying Tomcat's web.xml directly. Unlike the webserver variables, however, these must be set as an integer value denoting the number of minutes that should be allowed to elapse before timing a session out.

The first method is via a new environment variable on the liferay service:

SESSION_TIMEOUT

The second is via the portal.property:

session.timeout

Note that the liferay service will first check for the existence of the environment variable SESSION_TIMEOUT and will only check for the portal.property if the variable is not set. As such, the new environment variable takes precedence over any session.timeout portal.property set.

In the event that neither is set, liferay will configure the session timeout to be the default for Tomcat, which is 30 minutes.

Version 4 DXP Stack 2020.30.1 

Service Name	Previous Release	Current Release	Docker Images
Backup	4.0.3	4.0.3	liferaycloud/backup:4.0.3
CI	4.0.4	4.0.4	liferaycloud/jenkins:2.235.1-4.0.4
Database	4.0.1	4.0.2	liferaycloud/database:4.0.2
Liferay	4.0.1	4.0.2	liferaycloud/liferay-dxp:7.2-4.0.2 liferaycloud/liferay-dxp:7.1-4.0.2 liferaycloud/liferay-dxp:7.0-4.0.2
Search	4.0.0	4.0.0	liferaycloud/elasticsearch:6.8.6-4.0.0 liferaycloud/elasticsearch:2.4.6-4.0.0
Webserver	4.0.0	4.0.1	liferaycloud/nginx:1.16.1-4.0.1

 

Version 4 Update Instructions

Only Applicable to Version 4 Images

After upgrading your project using this guide, the Liferay Cloud image versions are no longer set inside of the gradle.properties file. They now need to set inside of the <service>/LCP.json file. Note, however, that the liferay service uses two image properties. The DXP Cloud image is set in the liferay/LCP.json file, but the liferay/dxp image is set in the gradle.properties. This change was made in order to facilitate easier deployment using the Liferay Cloud CLI.

liferay/LCP.json file would set the liferaycloud/liferay-dxp image:

"image":"liferaycloud/liferay-dxp:7.2-4.0.2"

liferay/gradle.properties file would set the liferay/dxp image:

liferay.workspace.docker.image.liferay=liferay/dxp:7.2.10-dxp-6-202006221121 

Once the LCP.json files are updated, commit the changes to your Git repository.

git add . && git commit -m "update dxp cloud stack to 2020.30.1"

After pushing these changes to the remote repository, a build will be created in Liferay Cloud and it is ready to deploy.

Version 4 Change Log

Service Name	Service Version	Ticket Number	Description
Database	4.0.2	LCP-7073	Create project secrets for read only user
Liferay	4.0.2	LCPE-1389	Unable to import big lar files
		LCP-7073	Create project secrets for read only user
Webserver	4.0.1	LCPE-1389	Unable to import big lar files

 

Version 3 DXP Stack 2020.30.1 

Service Name	Previous Release	Current Release	Docker Images
Backup	3.2.15	3.2.15	liferaycloud/backup:3.2.15
CI	3.2.8	3.2.8	liferaycloud/jenkins:2.235.1-3.2.8
Database	3.2.10	3.2.11	liferaycloud/database:3.2.11
Liferay	3.0.24	3.0.25	liferaycloud/liferay-dxp:7.2.10-sp1-fp5-3.0.25 liferaycloud/liferay-dxp:7.1.10-ga1-fp17-3.0.25 liferaycloud/liferay-dxp:7.0.10-ga1-fp91-3.0.25
Search	3.0.8	3.0.8	liferaycloud/elasticsearch:6.8.6-3.0.8 liferaycloud/elasticsearch:2.4.6-3.0.8
Webserver	3.2.0	3.2.1	liferaycloud/nginx:1.16.1-3.2.1

 

Version 3 Update Instructions

To apply these updates, update the gradle.properties file the project root folder with the new docker image tags. Here is an example of applying update 2020.30.1 for a 7.2 Liferay project:

liferay.workspace.lcp.backup.image=liferaycloud/backup:3.2.15
liferay.workspace.lcp.database.image=liferaycloud/database:3.2.11
liferay.workspace.lcp.search.image=liferaycloud/elasticsearch:6.8.6-3.0.8
liferay.workspace.lcp.liferay.image=liferaycloud/liferay-dxp:7.2.10-sp1-fp5-3.0.25
liferay.workspace.lcp.webserver.image=liferaycloud/nginx:1.16.1-3.2.1
liferay.workspace.lcp.jenkins.image=liferaycloud/jenkins:2.235.1-3.2.8

Once the gradle.properties file contains the updates, commit the changes to your Git repository.

git add gradle.properties && git commit -m "update dxp cloud stack to 2020.30.1"

After pushing these changes to the remote repository, a build will be created in Liferay Cloud and it is ready to deploy.

 

Version 3 Change Log

Service Name	Service Version	Ticket Number	Description
Database	3.2.11	LCP-7073	Create project secrets for read only user
Liferay	3.0.25	LCPE-1389	Unable to import big lar files
		LCP-7073	Create project secrets for read only user
Webserver	3.2.1	LCPE-1389	Unable to import big lar files
		LCP-6136	Missing build activity when deploying build with blacklisted image