Re: WO and Memory Management
Re: WO and Memory Management
- Subject: Re: WO and Memory Management
- From: Owen McKerrow <email@hidden>
- Date: Fri, 14 Jul 2006 15:37:08 +1000
Yes a couple of days ago we were.
Although we seem to be past them now and are dealing with the issue
of WO not appearing to let go of the memory it uses and it having
"broken pipe" issues.
Owen McKerrow
WebMaster, emlab
Ph : +61 02 4221 5517
http://emlab.uow.edu.au
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - -
"I like the way this project has somehow, against all common sense,
got itself made."
- Peter Jackson, "The Lord of The Rings"
On 14/07/2006, at 3:33 PM, email@hidden wrote:
Hello Owen;
its better to explicitly call System.gc() in WO App's. Whats the
rule of thumb here in terms of how often, is there a better spot
than others etc etc ?
It is only ever a hint, never a demand. I have resorted to this
infrequently.
That's correct, but I think the problem arises that if it does
decide to do a full-on garbage collect then it has a tendency to
freeze all of the threads for a bit while it does it. This can
lead to jittery responses from the application.
Are you actually getting "OutOfMemoryException"-s logged?
cheers.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40uow.edu.au
This email sent to email@hidden
_______________________________________________
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