IBM Support

Time Zones and delay in the Agent server Trigger.

Troubleshooting


Problem

Time Zones and delay in the Agent server Trigger.

Symptom

Assume the agent server is Self Triggered with trigger interval set to 2 min.

We saw an instance in which the agent is getting triggered every 7 hours even though the trigger interval is set to 2 mins. Following is a pattern of triggers taken from the logs,

15:25:19,826:DEBUG :Thread-15_XXX_SCHEDULE_ORDER: Invoking getJobs now
22:27:35,421:DEBUG :Thread-14_XXX_SCHEDULE_ORDER: Invoking getJobs now
05:29:37,262:DEBUG :Thread-15_XXX_SCHEDULE_ORDER: Invoking getJobs now

If we see the above excerpt from logs, the agent is being triggered every 7 hours 2 mins.

Resolving The Problem

This issue was happening because Database is in the GMT time zone and the appserver and integaration server were in PST, due to which MODIFYTS( an attribute in YFS_OBJECT_LOCK table) was getting set to a higher value(database time).
This attribute is updated after every trigger.
When the next trigger happens, YCPSchedulableTrigger(which does the job of putting the trigger) will see whether the (MODIFYTS + Trigger Interval) < SYSDATE, if YES then it will put a trigger.
We should make sure that all the components(application/agent/integration/database) are in the same time zone.

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

Historical Number

NFX7907

Document Information

Modified date:
16 June 2018

UID

swg21553671