Indeed, we adjust that value automatically when setting up a new installation. The default value (64mg I believe) is
simply too low to support a busy application or multiple sites.

-Mark

  -----Original Message-----
  From: Steven Erat [mailto:[EMAIL PROTECTED]
  Sent: Monday, June 28, 2004 3:56 PM
  To: CF-Talk
  Subject: RE: CFMX java.lang.OutOfMemoryError

  Brook,

  This Technote describes the problem and offers a solution:

  <http://www.macromedia.com/support/coldfusion/ts/documents/java_lang_outofme
  mory.htm>
  http://www.macromedia.com/support/coldfusion/ts/documents/java_lang_outofmem
  ory.htm

  The key characteristic of the error is that it is followed by the <<no stack
  trace available>> line.  When the error occurs in this context, the typical
  solution is to adjust the size of the Permanent Generation in the JVM.

  See also Pete Freitag's blog:
  http://www.petefreitag.com/item/139.cfm
  <http://www.petefreitag.com/item/139.cfm>
  http://www.petefreitag.com/articles/gctuning/
  <http://www.petefreitag.com/articles/gctuning/>

  -Steven Erat

    _____

  From: Brook Davies [mailto:[EMAIL PROTECTED]
  Sent: Monday, June 28, 2004 4:16 PM
  To: CF-Talk
  Subject: CFMX java.lang.OutOfMemoryError

  I have posted my log file (just todays pertinent bit) to
  http://www.logiforms.com/default-event.txt. Can anyone look at it and see
  what the $%^& is going on? Its filled with these entries:

  [0]java.lang.OutOfMemoryError
           <<no stack trace available>>

  My Server has 3 gigs of Ram, I don't know whats going on, so many things
  related to CFMX are acting strange right now...

  Brook
    _____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to