{"id":7463,"date":"2015-08-27T21:22:16","date_gmt":"2015-08-28T04:22:16","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/?p=7463"},"modified":"2020-08-27T16:28:40","modified_gmt":"2020-08-27T23:28:40","slug":"kb0009823-com-ephesoft-dcma-core-service-serverheartbeatmonitor-fatal-transport-error","status":"publish","type":"post","link":"https:\/\/ephesoft.com\/docs\/kb0009823-com-ephesoft-dcma-core-service-serverheartbeatmonitor-fatal-transport-error\/","title":{"rendered":"KB0009823 [com.ephesoft.dcma.core.service.ServerHeartBeatMonitor] – Fatal transport error"},"content":{"rendered":"

Applicable Ephesoft Transact Versions:<\/strong> 4.x<\/span><\/p>\n

Issue:\u00a0<\/strong><\/p>\n

A server may be down if the following error log is reported:<\/span><\/p>\n

[com.ephesoft.dcma.core.service.ServerHeartBeatMonitor] \u2013 Fatal transport error<\/span><\/p>\n

The heartbeat service is responsible for checking whether the servers registered in the database are still active. This is important for service failover assignments. However, if the reported server is active, then the following may apply:<\/span><\/p>\n