I have a test that has a once per week irregular schedule. It is an Active Script test that sends a request to a remote server which then makes a phone call.
Most of the time the test executes the script twice. This is evidenced by getting two calls and by two log files generated by the script. The recurrences column in the monitor is, however, only incremented once.
If I call the script via the Test button in the Test Properties dialog, it only executes once.
My system is running XP Professional Version 2002 Service Pack 1
The test details: Method = Script
;--- Common properties ---
;DestFolder = Mon1\Daily Sanity Test\
Title = 1. Monday Sanity Test
Comment = Perlscript: sas-sanitytest.pl"
RelatedURL =
ScheduleMode= OneTestPerWeek
ScheduleDay = 1
ScheduleTime= 07:00:00
Alerts = !!CRITICAL (1try)
ReverseAlert= No
UnknownIsBad= Yes
UseCommonLog= Yes
PrivLogMode = Default
CommLogMode = Default
;--- Test specific properties ---
ExternalFile= C:\Program Files\HostMonitor5\sas-sanitytest.pl
Language = Perlscript
Timeout = 20000
AllowUI = No
UseMacros = Yes
Irregular Schedule Test run twice
Thank you, Alex.
It must have been two copies running, since when I exited the window on my screen, it showed the monitor as still running.
I must have opened a second copy, several days ago, from the desktop while a running monitor was minimized.
I exited all copies and checked the process list to make sure no instance was running. I then restarted by opening a desktop icon, minimized the window and repeated the open from the desktop icon. Sure enough, a second instance started.
That would explain why sometimes only one call would happen.
I assume that the recurrences count displayed in the tableis a in memory value and reflects only the instance of the monitor that ran the test. This is what confused me.
Thanks again for pointing out my pilot error. The proof is in tomorrow morning's test.
It must have been two copies running, since when I exited the window on my screen, it showed the monitor as still running.
I must have opened a second copy, several days ago, from the desktop while a running monitor was minimized.
I exited all copies and checked the process list to make sure no instance was running. I then restarted by opening a desktop icon, minimized the window and repeated the open from the desktop icon. Sure enough, a second instance started.
That would explain why sometimes only one call would happen.
I assume that the recurrences count displayed in the tableis a in memory value and reflects only the instance of the monitor that ran the test. This is what confused me.
Thanks again for pointing out my pilot error. The proof is in tomorrow morning's test.
Yes, if you start several instances, each instance performs tests independently. Each copy of HostMonitor will perform tests and increase its own copy of recurrences counterI assume that the recurrences count displayed in the tableis a in memory value and reflects only the instance of the monitor that ran the test.
Regards
Alex