Environment
Sentinel 5.1.3 Sentinel Control Center
Sentinel 6.0.xx
Sentinel 6.0.xx Sentinel Control Center
Situation
Periodically Sentinel Control Center (SCC) will loose connection
and it will never reconnect.
There are several workstations running SCC with multiple active views running.
The only way to bring the whole thing back is to restart Sentinel.
There are several workstations running SCC with multiple active views running.
The only way to bring the whole thing back is to restart Sentinel.
Resolution
The DAS Run Time (DAS_RT) process is responsible for updating SCC
and the active views. A typical or default installation of
Sentinel allocates 256 MB of RAM to the DAS_RT process. The
DAS_RT logs were reviewed and analyzed. The DAS_RT logs
contained java.lang.OutOfMemoryError messages. The amount of
memory allocated to DAS_RT was increased from 256 MB to 1024
MB. The Sentinel server was rebooted and the problem went
away. To change the amount of memory allocated to DAS_RT,
please open the configuration.xml file and search for the
following:
-Dsrv_name=DAS_RT
Change the -Xmx256m to -Xmx1024m. NOTE: This change assumes that you have sufficient RAM in your system to handle this memory increase. If you do not have sufficient memory, you may consider increasing the amount of physical RAM in your Sentinel server, or move the Sentinel services to a server with more memoryresources. Alternately, you can reduce the number of workstations using SCC and also reduce the number of active views that you have enabled.
-Dsrv_name=DAS_RT
Change the -Xmx256m to -Xmx1024m. NOTE: This change assumes that you have sufficient RAM in your system to handle this memory increase. If you do not have sufficient memory, you may consider increasing the amount of physical RAM in your Sentinel server, or move the Sentinel services to a server with more memoryresources. Alternately, you can reduce the number of workstations using SCC and also reduce the number of active views that you have enabled.