• 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: Out of error debugging
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Out of error debugging


  • Subject: Re: Out of error debugging
  • From: Art Isbell <email@hidden>
  • Date: Thu, 28 Jul 2005 09:32:02 -1000

On Jul 28, 2005, at 3:10 AM, Helge Städtler wrote:

you can increase the "survivetime" significantly by using following
parameters as launchcommands (this is what my apps run with for now over 2
years without problems):


-Djava.awt.headless=true -Xmx1024m -XX:NewSize=2m -Xms1024m

but sooner or later this memory-error will haunt you.

Scheduling instances to restart regularly can be a workaround.

There must be some downside to setting the maximum JVM size to be very large. Otherwise, why can a process set its own maximum JVM size via a Java property? What are the disadvantages? Does this cause the OS kernel to preallocate memory possibly to the detriment of other processes?

Aloha,
Art

_______________________________________________
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: Out of error debugging
      • From: Arturo Perez <email@hidden>
References: 
 >Re: Out of error debugging (From: Helge Städtler <email@hidden>)

  • Prev by Date: Re: EOF and 100% Java client app
  • Next by Date: Re: EOF and 100% Java client app
  • Previous by thread: Re: Out of error debugging
  • Next by thread: Re: Out of error debugging
  • Index(es):
    • Date
    • Thread