-
Type:
Bug
-
Status: Closed
-
Resolution: Won't Fix
-
Affects Version/s: 7.2.0 GA1
-
Fix Version/s: None
-
Component/s: Fault Tolerance, Portal Configuration
-
Labels:None
The Education team is currently working on updating the Clustering section of the DevOps course. We are using two tomcat instances in Docker containers and have not been able to get clustering to work properly. The first node will start up as expected, but the second node throws various errors and does not start.
We also tried to enable clustering locally, not in containers and ran into the same issue.
The stack is made up of two 7.2 tomcat clusters connecting to a MySQL db.
Docker:
Image from liferay/portal: 7.2.0-ga1
Docker v 2.0.0.3 (31259) on Windows 10
Dockerfiles and logs attached
(You'll see there are two Dockerfiles in the attached folder. We were unable to get clustering working pulling from the official docker repo or when referencing local bundles)
Local:
- MacOSX 10.14.5
- MySQL 8
- OpenJDK 11
- liferay-dxp-tomcat-7.2.10-ga1-20190531140450482.tar (edited)
Steps taken for running local setup:
-create folder called `liferay-cluster`
-create 2 sub folders: `cluster-1` and `cluster-2`
-unzip tomcat bundle in each folder
-Added portal-ext with properties
-added mysql connector jar to lib/ext
-modified `server.xml` for bundle in `cluster-2`
-started bundle in `cluster-1` folder, waited, then completed basic config
-started bundle in `cluster-2` folder
Expected: navigating to localhost:8282 using a different browser and see the liferay splash screen
Actual: Never navigates to liferay splash screen