tracker issue : CF-3129821

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

Can only deploy 2 instances

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/CannotReproduce

Reporter/Name(from Bugbase): Andrew Scott / Andrew Scott (Andrew Scott)

Created: 03/04/2012

Components: Web Container (Tomcat), Instance/Cluster Manager

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Public Beta /

Priority/Frequency: Major / All users will encounter

Locale/System: English / Win 2008 Server x64

Vote Count: 0

Problem Description: Deploying anymore than this will result in instance 3 and 4 etc, not being able to be started.

Steps to Reproduce:

Actual Result:

Expected Result:

Any Workarounds:

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

Watson Bug ID:	3129821

External Customer Info:
External Company:  
External Customer Name: ascott67
External Customer Email:  
External Test Config: My Hardware and Environment details:


  1. March 05, 2012 00:00:00: 1_CaptureStopInstanceCf10.PNG


Hi, Can you give a more detailed repro case? (Comment added from ex-user id:kamaiya)
Comment by Adobe D.
20392 | March 05, 2012 01:16:04 AM GMT
Sure. 1) Install ColdFusion 2) Create new instance 3) Start new instance 4) Create new instance 5) start new instance Step 5 will never start, and the instance remains in a stopped state. I have tried deleting it, rebooting the server, restarting CF nothing will make that 5th step happen. If this works for you, then I would be happy to create a video of me doing those steps, and showing you it will not be able to be started.
Comment by External U.
20393 | March 05, 2012 05:13:44 AM GMT
The logs of the 3rd instance have this in them. Either the server is already running or some other application is using the Shutdown port 8009.
Comment by External U.
20394 | March 05, 2012 06:42:26 AM GMT
Rebooting the server, seems to run the all instances. Seems like something is not being updated, somewhere while CF is running.
Comment by External U.
20395 | March 05, 2012 06:56:06 AM GMT
After rebooting the server and then trying to stop the 3rd instance, an error is shown, see attached image for more details.
Comment by External U.
20396 | March 05, 2012 06:58:51 AM GMT
I should also point out that it says it has stopped, and yet when I look into the windows services it is actually still running.
Comment by External U.
20397 | March 05, 2012 06:59:53 AM GMT
Actually scratch that, it has stopped.
Comment by External U.
20398 | March 05, 2012 07:00:15 AM GMT
Could this be some sort of set up issue? Could you send us the logs? We've been trying with multiple instances and have not seen this behavior. Others too have not reported this issue.
Comment by Vamseekrishna N.
20399 | April 16, 2012 02:05:39 AM GMT
What logs do you require?
Comment by External U.
20400 | April 16, 2012 02:08:29 AM GMT
ColdFusion/Instance start logs?
Comment by Vamseekrishna N.
20401 | April 16, 2012 02:12:49 AM GMT
It will not allow me to attach the log file, can you email or give me an email to send it to please.
Comment by External U.
20402 | April 16, 2012 06:24:00 PM GMT
Actually don't bother this is all the log file has in it. Either the server is already running or some other application is using the Shutdown port 8009.
Comment by External U.
20403 | April 16, 2012 06:24:23 PM GMT
It should also be noted that in my case the original ColdFusion 10 installation is with a window service. Here is how I can duplicate it 1) Deploy second instance with windows service, will install and run 2) Deploy 3rd instance without a windows service, will install but will not start 3) Deploy a 4th instance same as step 2 same results 4) Deploy a 5th with no windows service, and will install and start fine. I also hope that when this product is released that the time it takes to install an instance is greatly enhanced. In comparison to ColdFusion 9 this takes around 10 times longer to install an instance.
Comment by External U.
20404 | April 16, 2012 06:51:44 PM GMT
We are not able to reproduce this bug in latest build. If you still face this issue, let us know, we will reopen this bug. (Comment added from ex-user id:duttswam)
Comment by Adobe D.
20405 | December 04, 2014 03:25:13 AM GMT