FaqDebuggingProblems

I'm running into problems when trying to debug. What can I do?

Work through the questions below when you encounter problems while trying to start and work with the debugger:

If your application is a web application, an EJB module, or a J2EE application, has it been correctly deployed?

Do the following:

  1. In the Runtime window, expand the Servers node, start the server (if not started), expand the server's instance node, and expand the node applicable to the type of application in question. For example, for web applications, expand the server's Web Applications node.
  2. If you do not see a node for your application, it has not been correctly deployed.
  3. Deploy the application.

Are you behind a firewall?

Check that your proxy settings are correct. Depending on your proxy type do the following:

  • HTTP Proxy.
    Choose Tools > Setup Wizard. In the wizard, select the Use HTTP Proxy Server checkbox.
    Type the proxy host name in the Proxy Server Name field and the port number in the Port field.
    Click Finish.
  • SOCKS Proxy.
    You must pass the SOCKS proxy host and proxy port parameters to the JVM software when you start the IDE.
    On Microsoft Windows machines, use the IDE-HOME/etc/netbeans.conf file to pass the parameters.
    On UNIX and Linux machines, you can write a wrapper shell script. Go to Help > Help Contents for details.

Is the server running in debug mode?

Check that the server has been started in debug mode:

  1. In the Runtime window,
    expand the Servers node and check that the server is running.
    Note that even if it is running, it may not be running in debug mode.
  2. If it is not running, right-click it, choose Start/Stop Server,
    and click Start Server (Debug).
    If it is running, but you are not sure that it is running in debug mode,
    stop the server and restart it in debug mode.

Are the server's port and address set correctly?

Check that the jpda.address set in debug.properties matches the server's settings:

  1. Right-click the server's node in the Runtime window and choose Properties.
  2. In the Properties sheet:
    • Check the Debugging Port property (for socket connections).
      By default, it should be 9009 for the SJS Application Server or 11555 for the Tomcat Web Server.
    • Check the Name property (for shared memory connections).
      By default, it should be localhost4848 for the SJS application Server or tomcat_shared_memory_id for the Tomcat Web Server.
      If you change the server's Debugging Port property or Name property, make sure that it matches the related property in the debug.properties file.
  3. Close the Properties sheet and stop and restart the server, if you had already started it.

Check that the jpda.transport set in debug.properties matches the server's settings:

  1. Right-click the server's node in the Runtime window and choose Properties.
  2. In the Properties sheet, check the Debugging Type property:
    • dt_socket for socket connections
    • dt_shmem for shared memory (Windows)
      If you change the server's Debugging Type property, make sure that it matches the related property in the debug.properties file.
  3. Close the Properties sheet and stop and restart the server, if you had already started it.

  Applies to: NetBeans 4.0, 4.1, 5.x, 6.x
  Platforms: All
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo