Question
Service Start Issues
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
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
AdChoices