Jrun.exe in CF 9 always hogging all memory: how to stop it?

PS

Perhaps I have misinterpreted the question - How to stop CF9. Use SERVICES,MSC find the CF service, it could be called macromedia (I forget and do not have a CF9 to look at) and stop the service. Set the service to manual to disable it from starting upon a server reboot.

HTH, Carl.

Hi CB,

Like Charlie more questions than answers from me as well. What Java version is CF9 using? What version of CF9 is that?

CF9 could be running Java 6. Some versions of CF9 (9.0.1 and 9.0.2 not sure on 9.0.0) support Java 7. Worth noting Java 6 and 7 are both Oracle end of life. Java 8 is current tho not supported on similarly end of life CF9.

Regards, Carl.

When you say “hogging all the memory”, what do you mean? Are you looking at an OS-level report of memory use, and is the jrun.exe using “all of it”? How much memory total do you have on the machine? And how much is it reporting that jrun (CF) is using?

Or are you viewing something that reports the use of heap within CF? Are you saying that all the heap is being used?

And what do you see in the ColdFusion-out.log? This file is either in \runtime\logs, or in \logs if you are using the multiserver deployment. If you are having an outofmemory condition, it will be reported there (and it may not be about outofmemory in the heap). Search for that string in that log, focused especially on the time before you restart CF (after such a “crash”).

Finally, is this a 32-bit or 64-bit machine? If 64-bit, and if you have more memory available then CF is using, and if you are getting outofmemory errors in the heap, you could raise the heap still more. For instance, if total memory is 4g, and CF heap is only 1G, and you’re getting outofmemory heap errors, you could try raising the CF heap to 2G.

But that’s NOT the solution if you’re on 32-bit (you can’t set the CF heap to more than about1.3g typically), or if you do NOT have available memory. It’s also NOT the solution if you are NOT getting outofmemory heap errors. There can be other outofmemory errors you may find, and those may indicate that the solution if NOT to raise the heap. We can’t really tell until you give us more info.

Let us know if this helps

/charlie