L
Laura Stern
Guest
Actually, I was not thinking of this case. What I meant before was that if a stop condition is caught and NOT re-thrown then I could see why you would not want to see the error in the log. It was completely handled. However, in this case, even if the condition was originally caught, you are throwing it back to the client. So at some level it is not being caught on the server side. Our original intent was to log any message associated with an uncaught Stop condition even if it was sent back to the client. Interestingly, for the lock conflict case, we originally were NOT writing the message to the server log. But we got push-back internally from various parties that this was a bug and I fixed it! So now you definitely WILL get the lock-wait timeout message in the server log even if the stop object is sent back to the client. Personally, I think I agree with you on this! You could log a bug and we can hash it out again. But it would be REALLY helpful if others out there would weigh in on this.
Continue reading...
Continue reading...