• 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: Debugging Memory?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debugging Memory?


  • Subject: Re: Debugging Memory?
  • From: James Cicenia <email@hidden>
  • Date: Tue, 12 Jul 2005 10:52:06 -0500

The code I added was minor, however, I did add a custom component to my D2W report generator. Just a minor little component to popup a window
with the project object in it. The rest of the code was really mostly cosmetic changes.


Now on to application settings. I have never ever set anything in the monitor. I am running a default monitor installation while running my app on a
1 gig mac mini. Where are the max and min heap sizes set? Didn't see any such setting in the monitor.


A memory newbie here,
- James

On Jul 12, 2005, at 10:40 AM, Chuck Hill wrote:


On Jul 12, 2005, at 7:59 AM, James Cicenia wrote:


Hello -

Recently,,,, maybe because of new users, etc., I have been getting debilitating error messages that lock my server...

Up until now, or my latest push of code I have had very few problems, now I am having a lot. Anyway here is the error that killed my app:

[2005-07-12 08:33:14 CDT] <WorkerThread7> <com.webobjects.appserver._private.WOComponentRequestHandler>: Exception occurred while handling request:
com.webobjects.foundation.NSForwardException [java.lang.OutOfMemoryError] null
[2005-07-12 08:33:42 CDT] <WorkerThread5> <WOWorkerThread id=5 socket=null> Throwable occurred: java.lang.OutOfMemoryError
[2005-07-12 08:33:42 CDT] <WorkerThread5> <WOWorkerThread id=5 socket=null> Workerthread exiting due to error, respawning with ID 10005...
com.webobjects.foundation.NSForwardException for java.lang.OutOfMemoryError


How does one debug this kind of problem in WebObjects? Is there a memory leak in WebObjects?


Not that I know of, but there might be one in your code. :-)



up to now I have only been restarting the application
weekly, maybe it has to be nightly?


That is a possible work around.



Any thoughts would be greatly appreciated


I can think of a few possibilities:
1. A recent code change introduced a memory leak / memory using bug
2. A sudden increase in data size / number of users has increased the memory the app needs to run
3 (related to 2) You are not allocating enough memory to the application


What min / max heap size are you launching the app with?


Chuck

--
Practical WebObjects - a book for intermediate WebObjects developers who want to increase their overall knowledge of WebObjects, or those who are trying to solve specific application development 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: Debugging Memory?
      • From: Robert Walker <email@hidden>
    • Re: Debugging Memory?
      • From: David Holt <email@hidden>
References: 
 >Debugging Memory? (From: James Cicenia <email@hidden>)
 >Re: Debugging Memory? (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Debugging Memory?
  • Next by Date: Re: Debugging Memory?
  • Previous by thread: Re: Debugging Memory?
  • Next by thread: Re: Debugging Memory?
  • Index(es):
    • Date
    • Thread