In the logging mechanism, I would check what the last time logged was. If it was less than 10 minutes, don't log. If greater, then drop a log entry and then reset the counter.
All I can say is a note of encouragement and an ancillary example. I've run West-Wind applications for months and the memory usage was stable, and no errors. (Other than the ones that I created. <g>) These apps were being hit thousands of times an hour, 24 hours a day. As another thought, could you have a task shutdown the app and restart it once an hour? Lew Schwartz wrote: > That's the thing that reminds me of the old memory leak problems: the > app needs to switch many objects into & out of activity rapidly, eg read > 10 bytes from the data feed, find the object to handle the bytes etc... > Lots of this stuff so the logging frequency would probably have to be > every few seconds which might add to the problem rather than solve it. > I'll keep the idea in mind as I look through other things, however. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
