Andrew, in that multiinstance deployment, did you have more than one CF instance configured? And if not, did you start the Admin instance? If not, then you only had one instance running, using what would be a shared jvm.config. As soon as you try to run one of them when the other is running, you should get the "no transports initialized" error. /charlie
_____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Scott Sent: Monday, October 22, 2007 12:51 AM To: [email protected] Subject: [cfaussie] Re: Anyone seen this error before? Charlie, I have a multiple instance of CF8 running on Windows 2003, and I have no problems with this and the debugger. But under ubuntu and linux have major problems with the debugger. Could it be that I somehow setup the separate configuration for JVM under windows 2003 without knowing it? Anyway, thanks all for the input. I would have thought that the debugger is something everyone is going to use that it would have setup multiple jvm configs from the start. Oh well.... Who knows why Adobe chose that path then. Andrew Scott Senior Coldfusion Developer Aegeon Pty. Ltd. www.aegeon.com.au Phone: +613 8676 4223 Mobile: 0404 998 273 From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Charlie Arehart (lists account) Sent: Monday, 22 October 2007 12:18 PM To: [email protected] Subject: [cfaussie] Re: Anyone seen this error before? Andrew (and others), you don't want to say that this isn't a problem on Windows. It'll bite anyone using the multiserver (multiple instance) configuration. As MrBuzzy hinted, it is that the default setup of the multiserver config is to have all instance share on jvm.config, and that's where you tell CF what port to use for the new CF8 debugger. The problem is that if any of the instances are up when another instance tries to come up, the other instances won't come up because the port is already in use. It can be tricky knowing what's happening and why. A real common example of this is that the cfusion instance goes down but the admin instance stays up. In this case, you only have 1 CF instance, but it doesn't matter. So MrBuzzy indicates that you need to create a separate jvm.config for each instance, but adds "who'd wannna do that[?]" Well, anyone who wants to use the debugger in multiserver mode will need to. No way around it (well, at least if one instance may ever go down). A couple blog entries discuss setting that up (not specific to the problem of the debugger but just for those who wanted to do it in general, such as perhaps to have other different JVM settings): http://mkruger.cfwebtools.com/index.cfm/2006/4/17/multiserver http://www.alagad.com/go/blog-entry/cf7-cf8-jrun-and-the-jvm HTH /charlie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
