B
Brian K. Maher
Guest
2. We have another way to know the objects/procedures that are leaked and where they were created. It's called logging. What we are missing here is a program to read the sometimes lengthy log file to cull out which objects are still around (created but not deleted). It is not difficult to write this in the ABL. In fact, someone in tech support recently wrote such a program and we could probably post it somewhere. It's already in the KB (see below). it’s for PASOE but can easily be modified for classic appserver log files. knowledgebase.progress.com/.../sample-code-for-analyzing-pasoe-agent-log-for-possible-memory-leaks
Continue reading...
Continue reading...