• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: java.lang.OutOfMemoryError with WODisplayGroup
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: java.lang.OutOfMemoryError with WODisplayGroup


  • Subject: Re: java.lang.OutOfMemoryError with WODisplayGroup
  • From: Denis Stanton <email@hidden>
  • Date: Thu, 9 Oct 2003 14:33:26 +1300

Hi Elizabeth

Thanks for taking the time to offer your help. If your domain name is any indication of your time zone you stayed up late to do so, so extra thanks. :-)

As you say, I don't think throwing more RAM at the problem should be the answer. That might get me through the installation phase, but my customer would expect this to keep working as the files grow. I need to find a proper way to be independent of the file size.

Your answer does give me the opportunity to ask something else that has been bothering me. How do I apply startup parameters when I am still in developer mode? I know where to add parameters to new deployed instances started with JavaMonitor, but right now I am just using Project Builder and clicking on the "Builder and run" hammer-and-monitor icon. I have tried to understand the many settings available under Targets", but without much success. Fortunately this gap in my knowledge does not prevent me from developing and running with WebObjects.

Denis


On Thursday, October 9, 2003, at 01:12 PM, Elizabeth Lynch wrote:

Denis

You can increase the amount of memory available to the Java VM by adding the app startup parameter:

	-XmxNNNm

eg

	-Xmx256m

to increase the memory to 256MB (I believe the default is 64MB).

However although that will probably fix the symptom, it may not be the 'correct' answer to the underlying problem; I expect others will be able to offer suggestions on that.


Is it really the case that a WODisplayGroup runs out of memory handling a table of between 3 and 6 thousand records? Is there something I should be doing to increase the available memory? Does the presence or absence of indexes, or the selection of a sort sequence in the WODisplayGroup make a difference? It does not seem to , but it occurred to me that the memory problem might crop up in sorting.


Liz
---
Liz Lynch www.plsys.co.uk
P&L
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.



Denis Stanton
email@hidden
Home:  (09) 533 0391
mobile: 021 1433622
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: java.lang.OutOfMemoryError with WODisplayGroup
      • From: Elizabeth Lynch <email@hidden>
    • Re: java.lang.OutOfMemoryError with WODisplayGroup
      • From: John Boynton <email@hidden>
References: 
 >Re: java.lang.OutOfMemoryError with WODisplayGroup (From: Elizabeth Lynch <email@hidden>)

  • Prev by Date: Re: webobjects-dev digest, Vol 1 #483 - 13 msgs
  • Next by Date: Re: java.lang.OutOfMemoryError with WODisplayGroup
  • Previous by thread: Re: java.lang.OutOfMemoryError with WODisplayGroup
  • Next by thread: Re: java.lang.OutOfMemoryError with WODisplayGroup
  • Index(es):
    • Date
    • Thread