IBM Support

Number of records from YFS_HEARTBEAT for active servers changes frequently when running HealthMonitor agent

Question & Answer


Question

Why does the number of records from YFS_HEARTBEAT vary while HealthMonitor agent is run? Query used to determine the number of active application servers - select count(*) from yfs_heartbeat where SERVER_TYPE='APPSERVER' and status='00';

Cause

The behavior is caused due to yfs.yantra.statistics.persist.interval being configured to use a value greater than yfs.heartbeat.refresh.interval.

Answer

Check the value of yfs.yantra.statistics.persist.interval and yfs.heartbeat.refresh.interval in yfs.properties and customer_overrides.properties.

yantra.statistics.persist.interval - Property to determine statistics logging time interval. Format of the property is Xm or Xh where X is an integer between 1 and 60 and M/m for minutes or H/h for hours.

yfs.heartbeat.refresh.interval - Property to determine heartbeat refresh time interval. Format of the property is Xm or Xh where X is an integer between 1 and 60 and M/m for minutes or H/h for hours

The Healthmonitor agent consider a JVM stale based on yfs.heartbeat.refresh.interval. But the heartbeat syncronization is made based on the value of yfs.yantra.statistics.persist.interval.

IBM® recommends that the value of property, yfs.heartbeat.refresh.interval, should be set greater than the value of the yantra.statistics.persist.interval property.

[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Performance","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"All Editions","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg21973149

Page Feedback