Skip to main content
R
RunEasy
Participant
January 9, 2011
Question

CF Sever is unable to process some templates whereas it can execute rest.

  • January 9, 2011
  • 2 replies
  • 395 views

Hi Everybody,

I am going through a very serious issue.Could anybody suggest??

There are around 200-300 users accessing coldfusion templates on a daily basis.

At times the coldfusion server responds to user's request.But more frequently it stops responding.

Sometimes part of the application is accessible and rests get hangged.

Coldfusion server  seems to be working fine when the load on server is low.As the load(no. of users) increases the template seems to

get hang.However CF server continues to try executing the template without resulting in error.As the execution reach  15-20 mins it gives 503-error.

Also it is observed that CF server settings has max jvm heap size as 512MB but during high load the heap size goes beyond 700 MB.

However when we increase the max heap size to 1024MB the problem still persistes.

We tried a workaround  to release memory from the object not currently in use.Even this seems to be not working.

Any pointers would be grateful.

Thanks.

    This topic has been closed for replies.

    2 replies

    C
    carl type3
    Legend
    January 10, 2011

    Hello,

    You do not say what CF version and edition as well as operating system and webserver, further details as to your configuration would help?

    You mention increasing max heap which can often help. I tend to find the minimum (initial) setting just as important. Perhaps some details of your JVM.CONFIG will assist? Configuration file is here ColdFusion\runtime\bin (or JRun4\bin for multiserver).

    HTH, Carl.

    D
    Dan_Bracuk
    Inspiring
    January 9, 2011

    We experience server overload from time to time as well.  In our case, the most common cause was a combination of poor code and impatient users.

    What would happen is that someone would make a page request (usually a form submission) where the results page had a slow query.  The user would get impatient and continue to attempt to submit the form.  That would eventually bring the application server to 100% cpu and we would have to restart cold fusion.

    We attempt to prevent this through by either using javascript to hide whatever the user selects after he does it the first time, or immediately going away from the first page.  This could be done by using an intermediate page, or by using cfflush on the results page.

    Maybe something similar is happening to you.

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