Skip to end of metadata
Go to start of metadata

 

Introduction

This section lists answers to some of the common problems encountered using FusionDebug. You can also find support information, updates and articles at the FusionDebug Website or go straight to the FAQ located there.

Common Problems

FusionDebug will not connect

The message is: “FusionDebug could not connect to the target system (machine:port)”.

Fixes

  • Check you have enabled Java debugging on a port that is available, and that the CFML server has started up correctly.
  • If you are using a non-standard port (not 8000), make sure you have correctly entered that port in the configuration dialog.
  • Make sure there are no firewalls or port restrictions in the network path between you and the target system.

FusionDebug will not launch

The message is: “FusionDebug can only connect to one target at once.”

Fixes

  • FusionDebug 3.6 is capable of attaching to one ColdFusion instance at a time. Terminate your previous session.
  • See Terminate on how to Terminate a previous session.

Expressions do not evaluate

The Expressions View can handle most expressions which are valid in ColdFusion.  A good rule of thumb is that  if you can write it inside a CFScript block, or within “#” characters, it's a valid expression.

Fixes

  • Expressions are evaluated and re-evaluated only in the context of a suspended thread.  If no thread is suspended, expressions are not evaluated.  If a thread is suspended, try clicking on it.  This will implicitly tell the Expressions View to re-evaluate its expressions for that thread.

Expressions listed as undefined

The Expressions View tried to evaluate the expression, but it either didn't return a value (for function calls) or the variable referenced in the function was not visible at the position the thread was suspended at.

I see many pages in Debug View

These threads have suspended because of a breakpoint.  Breakpoints fire whenever a request hits them.  If you see many pages in the Debug View, this is because a web browser requested that page, and the page hit a breakpoint.

Fixes

  • If you have a shared test server, we recommend disabling your breakpoints, or activating “Skip All Breakpoints” (See: Breakpoints View) after your breakpoint has fired, so requests from someone else do not suspend.

Breakpoints do not fire

Fixes

  • Check that FusionDebug is connected to your ColdFusion server (the Debug View looks similar to Figure 2 on Debug Target).
  • Check that the breakpoint which should fire has been looked up correctly.
    • The exact file in which this breakpoint is set is shown next to the breakpoint as the Server File.  If this is not showing the correct file, or shows “Breakpoint not active. Edit Source Code Lookups”, edit your Source Code Lookups using the Debug Configuration.

Breakpoints are not active

The message is: “Breakpoint not active. Edit Source Code Lookups.”
What this error means is that although you have told Eclipse that you want to set a breakpoint, FusionDebug couldn't work out in which file on your CFML server the breakpoint should actually be set. 

Fixes

  • Go back to the Source Code Lookup tab and make sure that your project is associated with the correct folder on the server
  • Changes to the Source Code Lookup tab take effect immediately after you select Apply, so this error will disappear as soon as FusionDebug can compute the real location of the breakpoint correctly.

Unable to display source code

If you step into a file whilst debugging, you may instead see a page containing the following message: "FusionDebug is unable to show you the source code for the CF Server". What this page means is that the server stepped into a file but FusionDebug couldn't work out which file in your Eclipse projects was associated with the one stepped into on the server. There are two possible reasons for this:

  • The project containing the source file is closed: If you read through the page, it will tell you which lookups were attempted and will also let you know if you have any closed projects. FusionDebug cannot show source code from closed projects. Make sure all related projects are open.
  • You are missing a mapping or have an incorrect lookup. At the top of the page you will see a button which will take you directly to the Source Code Lookup dialog. If you click on this then you will see that the CFML server Folder has already been filled out. All you need to do is enter the Eclipse Project/Folder information and you can add a new lookup.

Child Pages

 

 

 

 

  • No labels