TechNote (Archived)

Clustering Adobe Connect Enterprise Server 6 or Breeze 5.x with software SSL causes random failure when entering meetings

Issue

---

After configuring Adobe Connect Enterprise 6 or Breeze 5.x for clustering with software SSL, you find that some users randomly connect to a meeting room by entering the room multiple times.

To verify this issue, try to enter one meeting room 5 times. If you find that you can connect but at times you get an error and don't connect, look in the debug.log for the following:

Fker (d) RoomAssetManager 30407: Fail over check host=1, status=asset-host-active

Fker (d) RoomAssetManager 30407: Fail over check host=2, status=asset-host-backup

Fker (d) RoomAssetManager 30407: Fail over check isActive=true, isBackup=false, isOnlyHost=false

Reason

---

The reason you are seeing this is because the servers in the cluster are misconfigured for a software SSL cluster. One of the following may have occurred:

• You configured software SSL with a cluster for the first time and did not configure the RouteEntry.
• You had software SSL setup on a single server and you simply replicated the configuration from the single server and applied it to your new clustering environment.

For software SSL single-server setup, the RouteEntry in the Vhost.xml file is binding requests to the loopback 127.0.0.1 address, which wont work when the RTMP protocol tries to resolve on a different server in the cluster.

Solution

---

To fix this problem for Connect Professional 6, do the following:

1. Navigate to the c:\breeze\comserv\win32\conf\_defaultRoot_\_defaultVHost_ directory.
2. Open the Vhost.xml file in a text editor.
3. Search for the following line:
   <RouteEntry protocol="rtmp">*:*;127.0.0.1: ${ORIGIN_PORT}</RouteEntry>
4. Replace it with this line:
   <RouteEntry protocol="rtmp">*:*;*: ${ORIGIN_PORT}</RouteEntry>
5. Repeat steps 1 “ 4 on every server in the cluster.
6. Restart all Adobe Connect Enterprise 6 Services.

To fix this problem for 5.x, do the following:

1. Navigate to the c:\breeze\comserv\win32\conf\_defaultRoot_\remote\ for 5.x folder.
2. Open the Vhost.xml file in a text editor.
3. Search for the following line:
   <RouteEntry protocol="rtmp">*:*;127.0.0.1:1935</RouteEntry>
4. Replace it with this line:
   <RouteEntry protocol="rtmp">*:*;*:1935</RouteEntry>
5. Repeat steps 1 “ 4 on every server in the cluster.
6. Restart all Breeze 5.x services.

Search Support

---