Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Daily Data Availability Phase 2
-
Fix Version/s: Daily Data Availability Phase 2
-
Component/s: Event Listener
-
Labels:None
-
Environment:
staging-xml1 build 378
staging-svc2 build 954
Description
The UserAccountService sends events to the Event Listener (which uses persistent Active MQ) based on time zones. All events have string dates passed in. The Event Listener takes those messages and creates a script command with the parameters that come from the message. For four of the events, it ignores the date string passed in (the reason being is that the apps figure out the correct date).
This introduces space for a problem to occur. If the Event Listener / ActiveMQ are down overnight, when the script gets run, the app will figure out the wrong date (ie. if it figures out 'yesterday' and a day has gone by from when the script should have been run, 'yesterday' will resolve to 'today'). To that end, 'yesterday' will be skipped over completely. And a new event will get triggered, causing the same data to run twice.
The scripts are:
sepull3.sh
sepull147.sh
sepull164.sh
admax.sh
These scripts should have the correct date string passed in (the app will still map that date to account time).
Note admax.sh includes special rules that currently only get applied if no date is passed in. Will have to make those rules apply when a date is passed in, too.
