10.2B03
I have a long tx script that checks active transaction durations and sends an alert if the duration is greater than some threshold. The other night I got an alert with a duration of 1 408 592 009. That's 44 years for the curious. I have been using this kind of alert for years at multiple customers and this is the first time I see something bizarre like this.
The only thing that I can think of is that in the microsecond of my query the state changed to ACTIVE but the duration was still not set so it was random garbage.
Does this ring a bell for anyone?
certainly possible. or maybe its your code that's bad. (just kidding) most of the vst data is retrieved without any locking or concurrency control so occasionally things like this will happen. sometimes you will also see apparent minor inconsistencies like off-by-one errors or things not adding up exactly because the data are changing while you look at them. fortunately not too often.
As a workaround you can add a sanity check that you ignore the value if it exceeds a given length. Of course that won't eliminate all false positives unless all the bad values are long, but it's better than nothing.
Already done!
Thanks,