Debugging

Owned by Xiaoyan Kong (Unlicensed)
Last updated: Oct 25, 2012Version comment
2 min read

Nexaweb provides several tools and features that allow easy debugging of your application.

For information about debugging in Nexaweb Studio, see the Nexaweb Studio documentation.

Log Configuration

Both Nexaweb client and Nexaweb server support different levels of output for logs.  These levels include: 

  • debug
  • info
  • error
  • exception

You can configure log output levels for each named log in use.  The server log names vary with your application and the Nexaweb features your application uses.  For a list of the log names in use on the server, go to the Nexaweb Server Management Console. 

Configure server log levels by editing the following section in the server configuration file, nexaweb-server.xml:

<log-configuration default-log-level="info">
 <log name="XModify" log-level="debug"/>
 <log name="SessionManager" log-level="debug"/>
</log-configuration>

Configure client log levels by editing the following section in the client configuration file, nexaweb-client.xml:

Note: You cannot set a global, default log level for Nexaweb client logs. 

Debug Keys

You can access information useful for debugging through keyboard function keys. The Nexaweb Client maps some keyboard function keys to display information useful for debugging in the Java console or in a separate browser window. These keys are disabled by default; however, you can enable them by adding the following line to the nexaweb-client.xml configuration file:

 <debug-keys-enabled>true</debug-keys-enabled>

When you enable debug keys, your keyboard function keys operate as follows: 

 

Function Key Description

F1 and F2

Prints the client DOM with or without auto-generated IDs.

You can check this for correctness or copy and paste it into another file to use as a start page and easily replicate the state you were in.


F3

Launches the Nexaweb Server Management Console in another browser window.

F4Launches the Nexaweb Server Management Console in another window focused on the current session rather than the welcome page.
F5Prints all user documents available from the client side DocumentRegistry to the console with a small header.

Recording Traffic through TCP\IP Monitor

You can run your Nexaweb application through the TCP\IP Monitor which allows you to trace the requests and reponses between the Nexaweb Client and Server. You can use this to:

  • Verify the general workflow of the application
  • Check that the output XML generated by Servlets or JSP pages is well-formed and correct
  • See which URLs return 404 or other errors

To use the TCP\IP Monitor:

  • Your content must be uncompressed
  • You cannot use SSL between the server and client

See the Nexaseb Studio documentation for more information on using this tool inside Nexaweb Studio.

Server Management Console

The Server Management Console displays the state of services, sessions and performance meters.
 
You can access it by:
  • <application context>/Nexaweb/Services
  • The F3 function key from any client.