VDN Information Synchronization Request Gets No Response

Publication Date:  2015-06-29 Views:  153 Downloads:  0
Issue Description
In the CMS load balancing scenario, the request for synchronizing VDN information gets no response when the VDN information to be synchronized is massive. 
Handling Process
1. Log in to Apache server 1 as the root user.
2. Open workers.properties.
vi /opt/lb/conf/workers.properties
Change the parameters in bold in the following information:
#define workers
worker.list=CMSController,status
 
#connection Tomcat Server01
worker.CMSServer1.port=9029
worker.CMSServer1.host=10.10.10.31
worker.CMSServer1.type=ajp13
worker.CMSServer1.lbfactor=1
worker.CMSServer1.socket_timeout=60
worker.CMSServer1.socket_connect_timeout=30000
worker.CMSServer1.connection_pool_timeout=20
worker.CMSServer1.socket_keepalive=False

#connection Tomcat Server02
worker.CMSServer2.port=9029
worker.CMSServer2.host=10.10.10.32
worker.CMSServer2.type=ajp13
worker.CMSServer2.lbfactor=1
worker.CMSServer2.socket_timeout=60
worker.CMSServer2.socket_connect_timeout=30000
worker.CMSServer2.connection_pool_timeout=20
worker.CMSServer2.socket_keepalive=False
...
3. Restart Apache server 1.
4. Refer step 1 through step 3 to modify the parameters in workers.properties of Apache server 2.
5. Synchronize VDN information again.
Root Cause
It takes a long period of time for the CMS system to synchronize massive VDN information. However, the default timeout period specified in the Apache configuration file is 30 seconds. As a result, the Apache servers time out before the synchronization is complete. (In this example, the Apache software and CMS system are co-deployed on the active/standby servers.)

END