Re: java.lang.outofmemory
Re: java.lang.outofmemory
- Subject: Re: java.lang.outofmemory
- From: Denis Stanton <email@hidden>
- Date: Wed, 8 Mar 2006 13:49:45 +1300
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 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.
Have you reached an agreement? Each new email seems to invalidate the previous advice (a bit like the old "how does WebObjects licensing work" discussion :-) )
It would really nice if one of you experts could say what combination of saveChanges(), dispose(), invalidateAllObjects(), system.gc() etc is most likely to avoid memory blowout when handling large data volumes, and then if the other experts could voice agreement ? I keep bookmarking what seems like definitive advice only to have it contradicted by a following message.
regards
Denis Stanton
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden