Kbase 19121: Apptivity CManager Loses Connection to Dmanager Under Load
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/13/1999 |
|
Apptivity CManager Loses Connection to Dmanager Under Load
KnowledgeBase number: 19121
This document applies to: Apptivity Server
Version and Release Number: 3.1
During periods of heavy congestion, the default heartbeat intervals
may not be large enough for heartbeats between the Component Manager
(CM) and Distrinution Manager (DM) to be processed in time. If a
heartbeat is not received within the specified interval, the CM may
treat this as if it has lost connectivity with the DM and therefore go
into shutdown mode. To prevent premature shutdown, increase the
following properties to a higher value:
apptivity.heartbeat
apptivity.cmanager.pause
apptivity.pmanager.pause
NOTE:
This information is listed in the Server section of the Apptivity 3.1
Release Notes as note 3748. In the Release Notes shipped on the
Apptivity 3.1 CD, there is a typographical error in this note. The
last property above is listed as apptivity.dmanager.pause, but there
is no such property.
The property apptivity.pmanager.pause is a property of the Proxy
Manager, and can be disregarded if you are not using the Proxy Manager
in your deployment configuration.
References To Written Documentation or Other KnowledgeBase Documents:
Apptivity 3.1 Release Notes
Apptivity 3.1 Deployment Guide