Re: java.lang.outofmemory

On Mar 8, 2006, at 12:53 PM, Chuck Hill wrote: On Mar 7, 2006, at 9:11 PM, Mike Schrag wrote: I ran into this same thing ... I'm guessing I must have been using pre-5.2, because when this topic came up prior to January again, I was going to post about this, but thought "I should write a test

Re: java.lang.outofmemory

Hi Mike, On Mar 7, 2006, at 9:11 PM, Mike Schrag wrote: This topic came up in January too -- Hopefully nobody minds me quoting myself :) Not at all, great information here! And I was away so I missed this episode when it was first on. :-P This is a description of the current behavior i

Re: java.lang.outofmemory

There is one additional option that can be used to ensure/override the memory setting for all instances (even if they are not included in the arguments in JavaMonitor).On the aggregate target there is a JVM_OPTIONS key in Expert View.  Entering the memory settings here will include them in the laun

Re: java.lang.outofmemory

On 7 Mar 2006, at 23:10, Randy Wigginton wrote: At the risk of appearing foolish to a lot of people… where do I adjust the memory setting in XCode? I’ve gone to the target, and pasted the command line changes into the “pure java” field. But my startup parameters don’t change. Where does

Re: java.lang.outofmemory

On 8 Mar 2006, at 00:08, Ken Anderson wrote: I used to think that too - anyone from the old days do :) Art proved me wrong though... Sounds like my head is stuck in the pre-5.2 memory model, which I need to fix. I'll need to compare against the docs I quoted, and find out if the incons

Re: java.lang.outofmemory

This topic came up in January too -- Hopefully nobody minds me quoting myself :) This is a description of the current behavior in 5.3 that one might be able to gather if one were to, say, decompile and review the entire process -- not that i would ever do this or condone it, of course -- b

Re: java.lang.outofmemory

On Mar 7, 2006, at 4:49 PM, Denis Stanton wrote: On 8/03/2006, at 12:54 PM, Art Isbell wrote: Your statement seems to contradict On 8/03/2006, at 1:08 PM, Ken Anderson wrote: I used to think that too ... Art proved me wrong though... Hi guys This has been an interesting discussion as

Re: java.lang.outofmemory

On Mar 7, 2006, at 2:49 PM, Denis Stanton wrote: This has been an interesting discussion as it touches on area that has caused me some grief - outOfMemory problems are hard to solve, partly because they tend to fail to record all the usual evidence. Possibly one of the reasons this type of

Re: java.lang.outofmemory

On 8/03/2006, at 12:54 PM, Art Isbell wrote:Your statement seems to contradict On 8/03/2006, at 1:08 PM, Ken Anderson wrote:I used to think that too ...  Art proved me wrong though...Hi guysThis has been an interesting discussion as it touches on area that has caused me some grief - outOfMemory pro

Re: java.lang.outofmemory

Paul, I used to think that too - anyone from the old days do :) Art proved me wrong though... Ken On Mar 7, 2006, at 6:39 PM, Paul Lynch wrote: On 7 Mar 2006, at 23:11, Art Isbell wrote: On Mar 7, 2006, at 1:00 PM, Paul Lynch wrote: saveChanges() doesn't release snapshots, unfortunate

Re: java.lang.outofmemory

On Mar 7, 2006, at 1:39 PM, Paul Lynch wrote: Snapshots are stored at a lower level than editing context, so they won't be released. Your statement seems to contradict : "The memory allocated for the database row

Re: java.lang.outofmemory

On 7 Mar 2006, at 23:11, Art Isbell wrote: On Mar 7, 2006, at 1:00 PM, Paul Lynch wrote: saveChanges() doesn't release snapshots, unfortunately, which I would surmise is the problem. But if snapshot reference counting is working as advertised, dereferencing the only editing context cont

Re: java.lang.outofmemory

On Mar 7, 2006, at 1:00 PM, Paul Lynch wrote: On 7 Mar 2006, at 22:46, Jacky Gagnon wrote: First, its not a good idea to use invalidateAllObjects() to free memory; call saveChanges more frequently or just fetch what you need. saveChanges() doesn't release snapshots, unfortunately, which

RE: java.lang.outofmemory

PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Walker Sent: Tuesday, March 07, 2006 5:58 PM To: WebObjects Dev Apple Subject: Re: java.lang.outofmemory   There are a number of things that can be done to resolve this.   1. Allow your application to use more memory by increasing the

Re: java.lang.outofmemory

On 7 Mar 2006, at 22:46, Jacky Gagnon wrote: First, its not a good idea to use invalidateAllObjects() to free memory; call saveChanges more frequently or just fetch what you need. saveChanges() doesn't release snapshots, unfortunately, which I would surmise is the problem. If you just w

Re: java.lang.outofmemory

There are a number of things that can be done to resolve this.1. Allow your application to use more memory by increasing the heap size.     [This is good if you are running your app with too little heap space]2. Make your application use less memory by qualifying your fetches more precisely.     [M

Re: java.lang.outofmemory

Hi Randy,First, its not a good idea to use invalidateAllObjects() to free memory;  call saveChanges more frequently or just fetch what you need.  System.gc() is good for debugging but  will not help you to solve your problem.If you really  need more memory you can adjust the maximum memory size of

Re: java.lang.outofmemory

You can increase the memory in the Monitor setup as well as in the Application where you can add some more memory in the Java Heap which will help in the memory management. On 3/7/06, Randy Wigginton <[EMAIL PROTECTED]> wrote: > > > > Hello, > > My program loads a great deal of data from the datab

java.lang.outofmemory

Hello, My program loads a great deal of data from the database.  I process it, then attempt to “free” the memory.  My code looks vaguely like this: For (all objects) { EOEditingContext tmp = new EOEditingContext();   tmp.invalidateAllObjects(); tmp = null; System.gc(); }   Even