tracker issue : CF-3310070

select a category, or use search below
(searches all categories and all time range)
Title:

coldfusion.exe not being restarted by coldfusionsvc.exe

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Dan Corrigan / Dan Corrigan (Dan Corrigan)

Created: 08/14/2012

Components: Web Container (Tomcat)

Versions: 10.0

Failure Type: Incorrect w/Workaround

Found In Build/Fixed In Build: Final / 282891

Priority/Frequency: Major / All users will encounter

Locale/System: English / Win 2003 Server

Vote Count: 3

Problem Description:Coldfusionsvc.exe does not restart coldfusion.exe, unless coldfusionsvc.exe itself is restarted.

Steps to Reproduce:With the CF Application service running use task manager in Winodws and kill ColdFusion.exe.  In previous CF versions (when it was jrun.exe) it would spawn a new process immediately as long was the jrunsvc.exe (or now coldfusionsvc.exe) was still running.

Actual Result: coldfusion.exe never restarts.  You must restart the Coldfusion application service to get coldfusion.exe to restart.

Expected Result:  coldfusion.exe should restart immediately if coldfusionsvc.exe is still running.

Any Workarounds: restart the service.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3310070

External Customer Info:
External Company:  
External Customer Name: booster94
External Customer Email:  
External Test Config: My Hardware and Environment details: Windows 2003 32-bit /IIS6/ coldfusion 10

Attachments:

Comments:

I would add, also, that the expected behavior was also if CF crashed on its own, not just if one killed it in task manager. The fact that neither now triggers a restart of CF in services is indeed lamentable.
Comment by External U.
18552 | August 15, 2012 08:47:13 AM GMT
Dan presented this to me initially, and I have confirmed it. Thanks for filing the bug, Dan. Let's hope others see it, vote for it. I'll pass it on to some others for consideration. More than that, let's hope Adobe will soon address it (or we may hear of a workaround or explanation, at least).
Vote by External U.
18554 | August 15, 2012 08:48:29 AM GMT
This should just plain work.
Vote by External U.
18555 | August 15, 2012 08:59:56 AM GMT
Behavior should definitely be corrected as this impacts fault tolerance.
Vote by External U.
18556 | August 15, 2012 11:05:21 AM GMT
This is tested and works as desired (Comment added from ex-user id:kkulkarn)
Comment by Adobe D.
18553 | January 31, 2013 07:29:06 AM GMT