ColdFusion 10 instance creation path issue
When ColdFusion 7 was released back in 2005, the ColdFusion team gave us the ability to create new instances (assuming we were running in multi-server mode) directly from the ColdFusion Administrator of the default 'cfusion' instance.
There were a number of quirks with the instance creation process, which resulted in some of us sticking with the old manual process as used in CF6.1
One of the instance creation issues related to new instances inheriting paths pointing to the cfusion instance rather than the path for the newly created instance.
This bug has found it's way into ColdFusion 10. Thankfully it's incredibly easy to work around.
Let me demonstrate the issue, and how to fix it.
To create additional instances with ColdFusion 10, you need to be running ColdFusion Enterprise, or be running in trial or developer mode. If you log into the default installation instance, called 'cfusion', you'll have the ability to create additional instances via the Enterprise Manager option.
What actually happens when you create a new instance, is that this cfusion instance is effectively cloned, thereby inheriting settings you've configured. There's obviously pros and cons to this.
One of the cons is that with pages such as Charting or Logging Settings, you simply need to 'touch' the pages (i.e. click submit without making any changes), and the default path of /ColdFusion10/cfusion/logs will find it's way into new instances you create.
if you don't 'touch' the page then the correct path of /ColdFusion10/<newinstance>/logs will correctly be set.
Thankfully you can just manually correct the paths if required.
I logged this as a bug back in 2005/6, and have done so again for ColdFusion 10. The bug number is 3208658 and can be viewed at https://bugbase.adobe.com/index.cfm?event=bug&id=3208658






There are no comments for this entry.
[Add Comment] [Subscribe to Comments]