This will be my first CFMeetup presentation and I’m both nervous and excited.

The link for the CFMeetup is http://www.meetup.com/coldfusionmeetup/calendar/11128508/.

UPDATE: I’ve attached the slides and XML snippet that I referenced in the presentation. The URL for the recording is http://experts.na3.acrobat.com/p39094247/. Thanks to everyone for attending and for all the feedback.

I ran into a situation while working on a MachII application running on Railo 3.1 where I REALLY need to see what was going on with the various variable scopes during the request cycle, so I decided tonight to see if I could get FusionDebug 3 Beta up and running with Railo and Tomcat.

Before we get started, I want to detail my particular setup and lay out some assumptions. My environment consists of the following components. Yours might be slightly different, but the basics should be the same.

• Apache 2.2.11 web server configured with one virtual host per client site
• Tomcat 6 installed into /opt/tomcat
• Apache forwards ColdFusion requests to Tomcat via AJP
• http://localhost web root is /Users/dskaggs/Sites/localhost/htdocs
• WEB-INF folder from exploded Railo 3.1 WAR file resides in the web root folder

Now for some assumptions:

• You can browse to a CFML page (either by going directly to Tomcat http://localhost:8080/someContext/test.cfm or through Apache http://localhost/test.cfm )
• You’ve installed FusionDebug into Eclipse using the instructions in the “Install FusionDebug into Eclipse” section here
• You’ve created a project in Eclipse that points to your site files
• You don’t have Tomcat starting as a daemon or Windows service

The first thing that you have to do is tell Tomcat to enable debugging on a specific TCP port. For this example the port number that we’re going to use is 8000 (the same as the documentation on the FusionDebug site). You do this by adding the following line of code to the catalina.sh file in the /bin folder under the Tomcat install directory (in my case /opt/tomcat/bin/catalina.sh). I added it directly under the large comment block at the top of the file.

CATALINA_OPTS=-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000

If you’re on Windows, this file is named catalina.bat and the format is slightly different:

set CATALINA_OPTS=-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000

Save the file and launch Tomcat. In my case, I launched it in a terminal window so I could see exactly what was going on using the command

cd /opt/tomcat/bin
sudo ./catalina.sh run

If everything worked correctly, you’ll see the following line near the top of the output to the console:

Listening for transport dt_socket at address: 8000

That concludes the configuration necessary on the Tomcat side. Now we need to get FusionDebug configured to connect to that port. In Eclipse, go to Window > Open Perspective > Other and choose FusionDebug from the list that appears in the popup window.

Then you’ll need to open up the Debug Configurations panel by going to Run > Debug Configurations. Find the entry for Fusion Debug in the left side, right click on it and choose “New” from the context menu. Enter a descriptive string in the Name: block at the top of the left side of the screen (I used simply Localhost). Then move to the configuration panel below with the 3 tabs (Connect, Source Code Lookup, and Common).

On the connect tab, enter localhost in the Host: block and 8000 in the Port: block.

On the Source Code Lookup tab, in the drop list that says “<All Projects>”, choose the Eclipse project that contains your files. In the drop list just to the right of the Project select box you just clicked on, choose the folder that corresponds to the web root of your site. Finally, enter the full file system path that corresponds to the folder you just chose and click the Add button. Click the Apply button to save the configuration. You can then click the Debug button at the bottom of the screen to start the debug session. If all goes well, you’ll see “FusionDebug (localhost:8000) (Connected)” in the Debug pane.

Now it’s just a matter of creating a test.cfm file (or using an existing file), setting some breakpoints and browsing to the file and you should see the execution stop at your breakpoint and be able to browse through the list.

After a while of debugging, I tried to set a few additional breakpoints and instead of showing the typical solid blue dot icon on the line where I set the breakpoint, the Eclipse debugger showed a dot with a question mark over it. I tried terminating and relaunching the debugging session, closing and restarting Eclipse and even setting a breakpoint in a different file–all to no avail. After checking the LiveDocs on Adobe.com, I found a support article that described the various icons that could be displayed as breakpoints and what they indicated.

This particular icon indicated that the copy in ColdFusion’s memory didn’t match what was in the editor. That led me to think that maybe I could clear the template cache in the CF Administrator and take care of the problem. Nope. So I poked around a little more and found two buttons I hadn’t noticed before. On the Debugger Settings page, there are buttons to stop and start the debugging server. Two quick clicks and I had restarted the debugging server. However, when I relaunched the debugging session in Eclipse, my icon returned to having the question mark.

]]> http://dan.skaggsfamily.ws/2007/03/17/stuck-in-dc/feed/ 0