Child pages
  • Troubleshooting

Download the complete documentation in PDF


Skip to end of metadata
Go to start of metadata

This section lists answers to some of the common problems encountered using FusionDebug.  You can also find support information, updates and articles at our website:

http://www.fusion-debug.com/fd/support.cfm

  • FusionDebug won't connect.  The message is: “FusionDebug could not connect to the target system (machine:port)”
    • 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 won't launch.  The message is: “FusionDebug can only connect to one target at once.”
    • FusionDebug 3.5 is capable of attaching to one ColdFusion instance at a time. Terminate your previous session (Terminate).
  • Expressions don't evaluate.
    • The Expressions View can handle most expressions which are valid in ColdFusion.  A good rule of thumb is:  if you can write it inside a CFScript block, or within “#” characters, it's a valid expression.
    • 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 are 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 lots of pages in the 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.

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

  • Breakpoints don't fire.
    • 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.
  • No labels