This is a PITA, I submitted an idea during the CF7 beta to address this, but alas it was not high priority. What I suggested is to add the instance name to the header of the CFadmin tool so you know which instance you are manipulating, easy to forget the ports, eh? I was able to do this as an experiment internally ;)
With the ease of creating new instances in CF7, maybe its time we asked for a dashboard, eh? Maybe it could look like the JRun JMC or something. DK On 12/6/05, Steven Erat <[EMAIL PROTECTED]> wrote: > George, > > What do you mean when you refer to the "main CFMX Admin"? What makes any > one of the five CF Admins the main CF Admin? Whether they are clustered or > not, you'd still have to go to each one independently to tune the settings, > unless you are using CFMX 7.01 on WebSphere Network Deploy where WebSphere > "federates" the changes from the "main" server to each of the clustered > nodes. > > To avoid the confusion when dealing with numerous instances, I usually turn > on each built-in webserver for each instance, and set unique ports for every > one, (e.g., 8510, 8511, 8512, etc) regardless of whether they are all > independent and each configured for external webserver instances or whether > they are clustered and configured collectively for one webserver instance. > Then test a sample page outside the CFAdmin using the built-in webserver on > its unique port to continue the guarantee that you are testing the intended > server. > > -Steven Erat > > > On 12/6/05, George Abraham <[EMAIL PROTECTED]> wrote: > > > > All, > > We are running CFMX Enterprise with multiple instances of CFMX on 5 > > different servers. I was trying to enable debugging on a particular > > instance > > A and I went into A's CFAdmin to do so. I checked the requisite boxes in > > the > > debugging page, set my client's IP in the IP page and then checked the web > > application to see if the exception was being displayed in a 'robust' > > manner. To my surprise, no, there wasn't any additional info. I finally > > had > > to enable robust exception information in the main CFMX Admin to show this > > additional info. Why is this necessary? Shouldn't each of the instances > > have > > independence in deiciding this kind of thing? Or am I overlooking > > something? > > > > Thanks, > > George > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:226239 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
