[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Make the PASOE logs less noisy in the event of (fully-handled) STOP conditions

  • Thread starter Thread starter Laura Stern
  • Start date Start date
Status
Not open for further replies.
L

Laura Stern

Guest
First of all, I just checked. If you catch the lock conflict condition, we will not output the message to the log. So a lot of what you are saying is moot. But I believe the case that started this whole discussion was not one where the condition was caught. It was one where the condition was thrown out from the top procedure running on an AppServer. Here the condition is not caught on the server, but indeed, it is thrown back to the client where it presumably can get caught. I believe I already said, from my prospective, you are preaching to the choir. It doesn't seem necessary to me to put the information into the appserver log if all the information on what went wrong is going back to the client. If all the information is not going back to the client (as with .NET clients, and prior to v12 (or 11.7.x?), java clients, or before we serialized error objects back to ABL clients), then the information DOES need to be in the AppServer log or no one will know what went wrong - only that something has gone wrong. But I wanted someone ELSE to chime in on this last point.

Continue reading...
 
Status
Not open for further replies.
Back
Top