L
Laura Stern
Guest
Yes, if the lock-wait timeout expires you will get a Stop condition, but as of 11.7 you can CATCH it by catching a Progress.Lang.LockConflict type. In 11.7, you need to use -catchStop to get this behavior. In 12 that will be the default. We agree that this lock conflict should never have been a Stop condition in the first place. The use of Stop in the old days was more prevalent for reasons that have been lost. And we understand that it would probably be easier if it was now just another type of error, catchable with Progress.Lang.Error. But we believe that making this change could break existing applications, so we opted to make it a catchable Stop condition.
Continue reading...
Continue reading...