D
dbeavon
Guest
Something is really odd about ABL agent logging in 11.7.5. For one thing it broke the ability to dynamically change logging levels while the PASOE instance is running. See: Progress KB - Unable to dynamically update the Pacific AppServer agents configuration and Changing PASOE configuration dynamically (follow-up question about changing logging levels) - Forum - OpenEdge Development - Progress Community However, there are other weird things going on as well. Consider this logging configuration. agentLogEntryTypes=ASPlumbing,4GLTrace agentLoggingLevel=1 For whatever reason, the new behavior of the agent for that configuration is to generate 4GLTrace output at logging level *2*. It appears that whatever new programming work was done between 11.7.4 and 11.7.5 in the area of ABL logging has caused more than one problem. It broke several things at the same time. (I only wish that we were able to get some benefits out of the new programming work, rather than just the bugs). My theory is that there is no such thing as "4GLTrace" for logging level 1. So the properties system is trying to be smarter than me and is "coercing" the logging level up to 2 in order for the output to appear in the logs. However, this is not how it worked in the past. Previously we were able to simply switch the logging level between 1 and 2 in order to include or exclude the 4GLTrace output. In other words, I'd rather that the system would "coerce away" the 4GL tracing output at logging level 1 like it used to, and pretend that I had not requested 4GLTrace as one of my log entry types. Has anyone else upgraded to 11.7.5 yet and experienced these types of issues?
Continue reading...
Continue reading...