• 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: Tracing GC while stalking an OutOfMemoryError
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tracing GC while stalking an OutOfMemoryError


  • Subject: Re: Tracing GC while stalking an OutOfMemoryError
  • From: Chuck Hill <email@hidden>
  • Date: Thu, 22 May 2008 10:43:27 -0700


On May 22, 2008, at 8:04 AM, Rick Innis wrote:

Hey folks,

I'm dealing with a WebObjects app that has suddenly started experiencing OutOfMemoryErrors.

Probably due to a gradual increase of data in the database and large to-many relationships. You might want to check the wiki for some advice on managing large relationships if that is the problem.




The platform is WebObjects 5.2.1, OS X 10.2.6, Java 1.3.1. Yes, it's a little behind the curve. In theory it's migrating to a newer server running 10.4 Real Soon Now, and has been for about a year.

To try and track this down, I added -verbose:gc to the command line, as well as adding -Xms128m to give it more memory and see if that eliminates the problem.

Even 128 might be low, but it is a place to start.


Thing is, though I can see that these have the desired effect when I run the app from ProjectBuilder (did I mention it's a little behind the curve?), I don't see the expected output in the logfile when I deploy the app. I've combed the archives and have tried adding them as "Additional VM Options" via ProjectBuilder, as "Additional Arguments" in WOMonitor, and as JVM_OPTIONS in "Expert View". None of them, as Arthur Dent might say, seem to do a dickie-bird's. I've done a clean build, and I've even undeployed and redeployed the app.

It's entirely possibly that the options are being picked up, but the output is going somewhere other than the WebObjects log. Is there a way to get System.out and System.err to redirect to the log file defined in WOMonitor, or should they be going there anyway?


They should all go there. Mercifully, the name is all that I recall of Project Builder. I'd cut to the chase and just manually edit the classpath file inside

App.woa/Contents/MacOS/MacOSClassPath.txt

And add them to the JVMOptions:

# JVMOptions       == verbose:gc -Xms128m

NOTE: the # is NOT a comment marker, leave it there


Chuck

--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects






_______________________________________________
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


  • Follow-Ups:
    • Re: Tracing GC while stalking an OutOfMemoryError
      • From: Simon McLean <email@hidden>
    • Re: Tracing GC while stalking an OutOfMemoryError
      • From: Mike Schrag <email@hidden>
    • Re: Tracing GC while stalking an OutOfMemoryError
      • From: Simon McLean <email@hidden>
References: 
 >Tracing GC while stalking an OutOfMemoryError (From: Rick Innis <email@hidden>)

  • Prev by Date: Re: [Wonder-disc] NSUndoManager is Mandatory for any EOEditingContext
  • Next by Date: Re: Tracing GC while stalking an OutOfMemoryError
  • Previous by thread: Tracing GC while stalking an OutOfMemoryError
  • Next by thread: Re: Tracing GC while stalking an OutOfMemoryError
  • Index(es):
    • Date
    • Thread