tracker issue : CF-3129822

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

Web Connector has no selection for instance

| View in Tracker

Status/Resolution/Reason: Closed/Deferred/NotEnoughTime

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: There is no way how to select which instance will be used for the web connector.

For example create instance name cfusion2 with the server manager, then run the web connector and try to assign a website with that instance. There is no way!!

Steps to Reproduce:

Actual Result:

Expected Result:

Any Workarounds:

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

Watson Bug ID:	3129822

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



When you create a new instance, the respective instance folder is created under C:\ColdFusion10 directory. Go to the instance, for eg of you have created an instance called cfusion2, then go to C:\ColdFusion10\cfusion2\runtime\bin and run wsconfig tool. Then configure the connector accordingly. Thus, connector is configured for the required instance. Let me know if you have any more concerns. (Comment added from ex-user id:kamaiya)
Comment by Adobe D.
20386 | March 05, 2012 01:21:22 AM GMT
Seriously? As this is installed an runable from the start menu, then this will need to be revised and changed on how this works. 1) 99.9% of people are going to know to got and press the start menu, go to the adobe folder and select ColdFusion 10 from the start menu and run the connector. 2) People are not going to understand what you have just described to me. This has got to be the worst decision or implementation, on anything that I have seen you guys do. This will be certainly be blogged, as the ugliest mistake Adobe has made, as nothing can ever top this stupid design decision at all. Seriously, what are you guys thinking here?
Comment by External U.
20387 | March 05, 2012 05:19:26 AM GMT
Well I just did this. Configured all the websites to the second instance, why because that is what people will accidently do. Run the tool remove the instance connector, and reinstall via the other. Now there is no way to reset the connector, it thinks it is already installed. Man you guys make some stupid decisions about this product, and this has got to be the worst of them all. ColdFusion haters are going to love this, massive problem you have introduced.
Comment by External U.
20388 | March 05, 2012 05:23:29 AM GMT
Btw if this was me here is how it should work. The connector be outside of the instance, and when it is run it reads in the instance xml file. Then it knows what instances have been installed, and you can gauge from here the directory where to do your stuff. This would enable the connector to work the same way as it has in the past, and would allow people to use it the same way that they have for 12 or more years. But seriously, how in the hell are people going to understand that the connector is in each instance when they are so used to going to the start menu, and running it from there? I always love how things are half implemented in ColdFusion, and this seriously takes the cake. I thought the fact that the java integration was only half implemented was the worst design decision of this product, that was until I came across this stupid implementation.
Comment by External U.
20389 | March 05, 2012 06:01:20 AM GMT
The decision to keep the wsconfig separate for each instance has been made for two reasons - each instance should be self contained and self sufficient. In the earlier model, the jvm.config, wsconfig_jvm.config and some other configuration were shared by all the instances which caused lot of issues which we have tried to fix. - It also gives the flexibility to users while applying hotfixes. Many a times administrator want to decide to apply the hotfixes to only a subset of instances. The previous model didn't allow this if the hotfix was related to connector. We have tried to fix that. I agree that there is some usability issue here because one has to go to each instance to configure the connector for it, it is not critical because there is an easy work around available. We will look into this usability aspect in the next release.
Comment by Rupesh K.
20390 | March 26, 2012 12:45:46 AM GMT