ColdFusion Debugger on OS X with Multiple instances

Hi Ben, Yes, you do need to use separate jvm.config files for debugging to work on the CF instances, and start them from command line as: jrun -config <path_to_jvm_config> -start <server_name> If you launch a server instance from CF admin, it will use one jvm.config (user specified). But if you launch from JMC, it is going to use the default (shared jvm.config in jrun/bin) jvm.config. Thanks, Dipanwita I'm running multiple instances of CF on my Mac with Apache and haven't been able to successfully use the line debugger. I can get all the tests to pass and the debugger even starts but when I set a break point and try to run a page the debugger doesn't show me anything. I have several virtual hosts set up each with their own instance of JRun running. I read on someone's blog that with windows you have to create separate jvm.config files for this to work but I'm not sure if this is the case for OS X. Is anyone running multiple instances that is using the line debugger successfully? Thanks, Ben

Ok, so I created a new jvm.config file named jvm_js.config I added -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5006 to the config file, started up CF via command line pointing to this new config file and changed the port in the CF Admin to 5006. I now get this error in Eclipse: "The debugger server is currently listening on port 50909. The port is not the debugger port set in the ColdFusion Administrator. This port is selected randomly each time the debugger server starts." Thanks, Ben ----- Excess quoted text cut - see Original Post for more -----

The port number you specify in the admin is for the JVM. The JVM listens at this port for debugger command from debugger server. The port number that you can specify in Java & JVM options in CF Admin using -DDEBUGGER_SERVER_PORT is for the debugger server. This is the port number at which debugger server listens for debugger commands from the Eclipse client. This port number need not be specified by the user. If not specified, ColdFusion launches the debugger server with any random available port, in your case 50909. This could be a problem if CF is behind firewall and the random port that debugger is listening is blocked by the firewall. In such cases users can tell ColdFusion not to use a random port, and specify the port number. User can then allow this port in the firewall. Please try changing the debugger server port number to something else in CF Admin. Thanks, Dipanwita Ok, so I created a new jvm.config file named jvm_js.config I added -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5006 to the config file, started up CF via command line pointing to this new config file and changed the port in the CF Admin to 5006. I now get this error in Eclipse: "The debugger server is currently listening on port 50909. The port is not the debugger port set in the ColdFusion Administrator. This port is selected randomly each time the debugger server starts." Thanks, Ben > Hi Ben, > > Yes, you do need to use separate jvm.config files for debugging to work ----- Excess quoted text cut - see Original Post for more ----- to ----- Excess quoted text cut - see Original Post for more ----- run > a > page the debugger doesn't show me anything. > > I have several virtual hosts set up each with their own instance of JRun ----- Excess quoted text cut - see Original Post for more -----

Thanks for the help Dipanwita. It works now!. Ben ----- Excess quoted text cut - see Original Post for more -----