• 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
java.lang.OutOfMemoryError with WODisplayGroup
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

java.lang.OutOfMemoryError with WODisplayGroup


  • Subject: java.lang.OutOfMemoryError with WODisplayGroup
  • From: Denis Stanton <email@hidden>
  • Date: Thu, 9 Oct 2003 12:25:35 +1300

I'm getting an OutOfMemoryError in a component that uses a WODisplayGroup to read a moderately large table

I have naively assumed that a WODisplayGroup set to display records in batches would only need to hold the current batch in memory, so the total table size would not be an issue. Is this overly simplistic?

I have built a table in MySQL and loaded 6,063 rows. Each row has 165 columns. I can't tell the data size in bytes, but the text file containing the SQL insert statement is about 7.5 MB. The columns are mixture of integer, date and varchar set to 16, 32 or sometimes 64. I guess loading into MySQL is going to expand the size beyond 7.5 MB, but not by an order of magnitude. A significant amount of data, but not a really large scale operation.

I have defined a simple Display Group WOComponent to allow me to inspect these data. I set the batch size to 10 and defined a display field for each attribute.

When I open this component there is a long delay and finally an OutOfMemoryError
In the past I have found error this is always the result of some accidental recursion in my programming. I was reluctant to believe that WebObjects simply can't handle a 6,063 line table. (Mac OS X 10.2.6, WebObjects 5.2.1, iMac G3 400, 512MB)


I trried dropping the table and rebuilding it with only a dozen records. It was OK
I added another 3000 records. Still OK
I added the full file up to 6,063. Out of memory.


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.

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: Art Isbell <email@hidden>
    • Re: java.lang.OutOfMemoryError with WODisplayGroup
      • From: Elizabeth Lynch <email@hidden>
References: 
 >Re: WebObjects and Panther (From: "Colin O'Brien" <email@hidden>)

  • Prev by Date: FW: Problem with example ComponentCommunication
  • Next by Date: Re: java.lang.OutOfMemoryError with WODisplayGroup
  • Previous by thread: Re: WebObjects and Panther
  • Next by thread: Re: java.lang.OutOfMemoryError with WODisplayGroup
  • Index(es):
    • Date
    • Thread