D
dbeavon
Guest
Would it work to use a different logging entry type? Or a different logging level? For each entry in the logs, it tells you what log entry type was in effect and what logging level caused the entry to be written. So you can decrease the logging level until you stop seeing the excessive logging, and you get information in less detail. if decreasing the logging level does not work, you can try a different logging entry type. I normally use these: ASPlumbing,DB.Connects,4GLTrace,4GLTrans But if 4GLTrace is too noisy, I take it out altogether (since "ASPlumbing" will show when a round trip to appserver is started and stopped, along with the external .p that is being called.) As a last resort, you do your own custom logging and rely on that instead of the built-in log entry types. Custom logging involves calling methods on the LOG-MANAGER. When doing your own custom logging, you can make it as sparse or verbose as needed. Hope this helps.
Continue reading...
Continue reading...