D
dbeavon
Guest
When you refer to "memory leaks within code executed on the AppServer" then I'm assuming you mean custom ABL code. (ie. not the Progess native/internal stuff). I can trim all inactive appserver sessions (my ABL sessions) and the OEE console will no longer show them listed within that agent. What doesn't make sense is that once my sessions are gone, and fresh sessions take their place, the working set of the process doesn't drop substantially. My understanding is that performing this operation should eliminate any reason for pointing fingers at my custom ABL code, because those ABL sessions, along with related ABL memory, should not exist anymore.
Continue reading...
Continue reading...