Skip to main content
S
splitzer
Inspiring
January 25, 2009
Question

jrun.exe memory leak

  • January 25, 2009
  • 1 reply
  • 4364 views
Hi,
I had my brand new test server setup earlier this month with everything clean installed. I'm having issue with jrun.exe memory usage skyrocketing to 500mb+. jrun.exe also makes the sql queries to respond slow. What i've been doing for past week is terminate the process, and restart the server.

Event after restarting, sometimes it instantly goes back to 500mb+ usage. I'm testing farely small application on this server, i dont think the application would be causing this issue.

I had the same problem before, thats why it lead me to get new test server, but now event on brand new system, jrun to repeat same issue.

Beside coldfusion, i have sql server 2008, which runs perfectly normal throughout the week.

Does anyone know the fix?

Syed
    This topic has been closed for replies.

    1 reply

    A
    Anonymous
    January 30, 2009
    Jrun's jvm memory usage is configurable in the jvm.config file. It is most likely the default startup is defaulting to take up a minimum of 500 MB. Different jvm's act differently and some are better at memory management than others. This isn't necessarily an indication of a memory leak, it's more the jvm's nature to act in this manner. No matter what it's probably peaking around 1.5 GB if I had to guess.

    I would look for other areas when it comes to performance, if it's a small application and the only thing running on the CF server. Look for things like unintentional loops, returning large record sets from SQL, large values in session variables. Also never store client variables in the registry. It could also be if you have large db tables, you may need some indexing in the database.
    S
    splitzerAuthor
    Inspiring
    January 30, 2009
    Hi,
    It actually happens sometimes right after i restart the service, or server, it shoots back to hi usage. Event if i have not started any applications.

    I think loop/sql leak should not apply to my case, atleast until i run the application atleast once.

    I would do some research before messing with jvm.config file. Thanks for the reference!
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices