Skip to main content
A
Anonymous
September 2, 2008
Question

Memory usage increases and server crashes

  • September 2, 2008
  • 3 replies
  • 437 views
As of about 1 week ago, we suddenly had issues with our server using all the allocated heap and eventually crawling to a halt where we have to manually restart the ColdFusion service. We have rolled back all code changes, but are still having the issue. Our specified heap size is 1.5GB. It takes about 1 hour for all of that to be used up as you can see in the image below.

We are thinking there are variables being created that still keep a reference in memory and aren't getting garbage collected. Here is a screenshot of our memory usage in just over 1 hour of the server being rebooted.

http://www.karaokewh.com/images/cf_memory.jpg
    This topic has been closed for replies.

    3 replies

    N
    Newsgroup_User
    Inspiring
    September 2, 2008
    > We are running CF 8 on Windows Server 2003 32-bit. I've using different applications that come bundled with JDK to do heap dumps and other analysis, but I haven't been able to find anything out.

    You can't allocate a 1.5GB heap on Windows.

    The maximum stable size I've managed to get is around 1GB.

    --
    Adam
    A
    Anonymous
    September 2, 2008
    We are running CF 8 on Windows Server 2003 32-bit. I've using different applications that come bundled with JDK to do heap dumps and other analysis, but I haven't been able to find anything out.
    A
    Anonymous
    September 2, 2008
    Could you give more specifics on your server, eg. CFVersion, OS (32 or 64), etc.

    I thing I can say is that if you are running a 32 bit OS, allocating 1.5 on your heap wouldn't help your server starting up. According to Sun, you can only allocation up to 1.8 (I think) GB of heap on 32bit JVM, although I've been only successful in allocating 1.4 - and even that takes time to restart. Also, the bigger the heap, the longer it takes for the GC to trigger. Again if you are running 32bit OS, I would lower it down to 1GB allocation, then get some stack traces to see whats causing the hangup. To get a stack trace, here is the link:

    http://www.adobe.com/go/tn_18339

    HTH.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices