D
dbeavon
Guest
Yes, the default lock-wait-timeout (10 second vs 30 min) is what causes STOP's to happen more frequently in PASOE. Now that STOP's are so much more common, we have started to introduce error-handling that is designed to consistently address the problem - or provide a better message to the user. Given the explicit error-handling, these "STOP" conditions don't need to be so noisy in the agent logs. (They don't need to be any more noisy than if we were to raise and then handle our own custom errors - via UNDO, THROW NEW Progress.Lang.AppError ). I was just wondering if it was possible to turn down the volume on these STOP's in the agent logs. The only approach I can think of is a bit risky (LOG-MANAGER:LOGGING-LEVEL to zero and then try to ensure that it gets changed back to 1 again in the future). It may have unintended consequences that extend beyond the "STOP" conditions. Hope this makes sense.
Continue reading...
Continue reading...