Jun 04
Error connecting to JVM for debugging at localhost:5005
Posted by James Netherton | Monday 04 June 2007 10:51 PM | In ColdFusion
I finally got the ColdFusion 8 debugger working from Eclipse. Kola, in my previous post, suggested tinkering with the JVM.config file and he was right. I installed ColdFusion in multiserver mode on top of JRun and it seems the necessary entries are not added to the JVM.config file in order for the ColdFusion debugger to operate.
So I stole and amended some of the parmeters that are used for the other ColdFusion debugger - FusionDebug. Here's what I needed to add into the JVM.config file:
-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005
The address parameter should match the port that the ColdFusion debugger is listening on.
Now I can set breakpoints in my code and step through it at runtime!
6 Comments
[Post comment]
1
Posted by kola | Monday 04 June 2007 7:14 PM
cool glad you got it working
2
Posted by charlie arehart | Saturday 28 July 2007 11:16 AM
Hey James, FWIW, I'd just like to share (for future readers) that the need to manually configure the multi-instance version as well as the jvm config entry details are both indeed documented by Adobe in the CF8 "Developer's Guide", in the section "Setting up ColdFusion to use the
Debugger". I'm sure many will miss that, though, so blog entries are indeed another way to get the word out. Thanks for sharing your experiences.
3
Posted by Kevin Penny | Tuesday 21 August 2007 10:02 PM
Thanks for the post - I am able to get my multi instance up and running no problem in 8 - however, i'm now noticing that now that I've changed my single jvm.config file in the bin dir - that after specifying a port number, and specifying that in one of the instances admin - and then attempting to start up any of the other instances - they won't start up. When I remove the line ',address=4131' (or whatever the port may be) - all instances start up just fine -
You seeing the same thing?? So when i tell the jvm config file to listen on a certain port, and then tell one of the instances what the debugging port is - none of the other instances start up - i can only start/stop the instance that i assigned that debug port to in it's cf admin area.
4
Posted by Kevin Penny | Tuesday 21 August 2007 10:11 PM
Ok - not to answer my own question - but maybe it has to do with the fact that I would have to separate each jvm.config for each server - and that the debugging will only work for a single server.
(http://www.fusion-reactor.com/support/kb/FDS-93.cf...) ?? maybe?
5
Posted by charlie arehart | Tuesday 21 August 2007 11:24 PM
Kevin, the solution to your problem is that you want to create a separate jvm.config for each instance (CF and the JRun Admin), or at least a separate one for the CF instance.
Rather than the FusionReactor KB, your problem is better addressed by the Adobe KB it points to: http://kb.adobe.com/selfservice/viewContent.do?ext...
You'd then cause the CF instance to start using that special jvm.config. Besides the command-line approach discussed in that KB, you can also do it while running CF as a service, as discussed in this blog entry:
http://www.doughughes.net/index.cfm?event=viewEntr...
Be sure to read the comments, including mine, for some useful additional info.
I actually thought about mentioning all this in my earlier reply here. I just new it would take all this explanation and I wondered if you would really hit the problem. You did, though, so here you go.
6
Posted by Kevin Penny | Wednesday 22 August 2007 11:09 AM
Thanks Charlie -
yup that was the case - I was a bit surprised - but I guess after I had successfully gotten the debugger to work - I had not attempted to turn on any of the other servers in the pool - so when I saw that error (no start up ability) I figured it must be the port case.
All working smooth now - each having their own special port to debug on - gotta love developing in that environment!