Skip to main content
May 24, 2007
Question

Service Start Issues

  • May 24, 2007
  • 13 replies
  • 988 views
I'm experiencing some "finicky" behavior with the CF Application Server. I recently (about 2 weeks ago) reformatted my laptop and repartitioned my drive. I'm currently running XP Pro with 512 ram. I have reinstalled CFMX7 and have it running as my web server (no IIS currently).

If the startup type for the CF Application Server service is set to automatic, when I boot my laptop it will start the jrunsvc.exe process, start a jrun.exe process, and then "hang". By "hang" I mean the jrun.exe process will climb to 99% processor usage and stay there indefinitely. When this happens the CF App Server never starts successfully. Kill process does not seem to work, and the only resolution I've found is to reboot my machine.

If I set the startup type to manual, the service does not start with my machine when it boots. If I open my services snap in immediately after I log into the machine, I can start the service, jrunsvc.exe runs, jrun.exe runs, the jrun.exe bounces between 40 and 70% processor usage for a minute or so, the jrun.exe grows to about 50k in memory usage, and then the jrun.exe processor usage drops back to 0 - 5% and things work like a charm. This only occurs if I start the CF App Server immediately after I log into my machine.

If I have been working on my machine for a while when I attempt to start the CF App Server from the services snap in (with or without programs running at the time), it exhibits identical behavior to what it does when I have the service set to automatic. I get jrunsvc.exe, a jrun.exe instance, and then the jrun.exe jumps to 99% and sits there indefinitely. Again, kill process on the jrun.exe doesn't work, the service never starts, and I'm forced to reboot to reclaim my processor.

As you can imagine, this is highly frustrating. If someone has encountered this, or can point me in the direction of a solution, that'd be great. Thanks,

--Daniel
This topic has been closed for replies.

13 replies

May 25, 2007
When you start it from the command line, unfortunately there is now way to eliminate DOS window. It has to be there, otherwise process will be killed.
Once you start CF from the command line, do you see anything? It is supposed to show everything that happens on the server, any exceptions and things like that.

Another idea here would be to enable JRun metrics and see what happens memory-wise and thread-wise. Based on your description it does not look like there are many people who are accessing your machine, so I wonder what we will see in JRun metrics. If you'd like to do that, check the following technote http://www.adobe.com/go/tn_19120. If you have standalone install (which looks like you do) make sure you check the note on the bottom of that technote.
After you have metrics enabled and CF restarted, they will be stored in your coldfusion-event.log file under C:/CFusionMX7/runtime/logs directory.
May 24, 2007
Not quite it doesn't seem, though I appreciate the assistance. I still seem to run into issues if I try to start the CF App Server through the services snap in. I was able to start it once after the above troubleshooting and it did ok, but about 2 hours later I stopped it to free the 50megs of memory, and then about 2 hours after that needed to start it again.

When I attempted to start it, I got the same behavior. The jrun.exe jumped to 99% and stayed there. I can lower it's processor priority so that other programs override it pretty easily and that seems to give me a bit of my performance back, but in order to eliminate the jrun.exe process I'm still forced to reboot.

If I start CF using the command line, is there a command to close the command window without stopping the service again? Ctrl-C will stop the service, but I would like to be able to close the command prompt without stopping the service.

Thanks again,

--Daniel
May 24, 2007
Great! So now when you start your services automatically jrun.exe does not go crazy anymore?
May 24, 2007
Oops. Didn't realize the slash direction was important in this one. That made a huge difference. I'll have to run some test after I've my machine up for a while and see how it does, but so far that seems to have done the trick. Thanks for all your help Dmitriy.
May 24, 2007
It should be java.home=C:/j2sdk1.4.2_13/jre
Make sure you have right slashes in there.
May 24, 2007
I went into the jvm.config file and attempted to modify this line:

java.home=C:\CFusionMX7\runtime\jre

to be this:

java.home=C:\j2sdk1.4.2_13\jre

Now when I attempt to run cfstart I get the following:

Error: no known VMs. (check for corrupt jvm.cfg file)

I've tried undoing the changes, but I'm still getting the error. :( I've now gone from not working some of the time to not working at all. Hopefully it's just something I entered wrong and can be corrected.

Thanks for all your help by the way, I appreciate it. I'd probably be lost without the online community.
May 24, 2007
It seems like if left long enough the command line will finish loading. It takes about 10 minutes a time, and then it will finally print several lines.

I'm currently installing the SDK and will test it when I can.
May 24, 2007
You did not even get to the point you got to last time? It does not look like it actually started.
Have you tried updating JVM? I would probably start with that. Go to http://java.sun.com/products/archive/j2se/1.4.2_13/index.html and download J2SDK, install it and then point your jvm.config file (C:/CFusionMX7/runtime/bin) to use that JVM. Then try again starting CF.
May 24, 2007
Update: After I attempted to run the server from command line, the jrun.exe hung up at 99% processor usage again and I had to reboot my machine. Upon reboot I went back into the command line and tried to start the server again. This is all that it returned:

C:\CFusionMX7\bin>cfstart
Starting Macromedia JRun 4.0 (Build 92909), coldfusion server

So far that's all I've received. My jrun.exe is at 99% and about 15k memory usage, and I am not sure how I should proceed next.
May 24, 2007
That is not a big deal. The file is actually located under C:/CFusionMX7/lib directory. Tis warning does not cause any issues and proper file is being found.