>We also tried to call periodically System.gc() but it didn't >produced any visible results so we aborted this approach.
The VM collects garbage regardless of whether you call System.gc() or not, System.gc() only allows you to suggest to the VM when might be a good time to run the garbage collector. >Does anyone knows a way to avoid this situation? Fix your code to remove memory leaks. Just because java has garbage collection does not mean programs can't have memory leaks. If you keep a reference to an object around, perhaps in a cache or static variable some place, it will never be garbage collected (because somebody has a reference to it) even if you never use that object again. Check out: http://www-106.ibm.com/developerworks/java/library/j-leaks/?dwzone=java For some suggestions on what to do. -- ______________________________________________________________________ Wilhelm Fitzpatrick | When we speak of free http://www.3roses.com/ | software we are referring [EMAIL PROTECTED] | to freedom not price. ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
