J
James Palmer
Guest
I'm not saying this is your cause, but Mike Banks said at the PASOE workshop I attended last month that this is something they've seen quite a bit with PASOE in production environments. As far as I remember the main culprit they've found is memory leaks within the code executed on the AppServer. You don't notice the leaks in classic AppServer as the agent shuts down at the end of processing. With PASOE sharing so much more, and agents sticking around so much longer, memory leaks become an issue. They suggested using Dynamic Object logging to look for objects that are created and not cleaned up as a starting point for finding these leaks. This KB applies: knowledgebase.progress.com/.../P133306 Obviously bare in mind (as I'm sure you would), that some objects shouldn't be cleaned up! It may also be a good idea to raise a case with tech support on this.
Continue reading...
Continue reading...