D
dbeavon
Guest
Thanks Fernando. When I first saw the message I assumed that my STOP-AFTER behavior was being "trumped" by the lock-wait. But then I examined the logs more closely to see the actual amount of time that had elapsed. Thankfully the actual timeout that was effective was the min of the two (stop-after and lock-wait). I'd guess that the message is some sort of a default that is shown for any preemptive interruptions.
Continue reading...
Continue reading...