Developers Getting Started With i2b2
Space shortcuts
Space Tools
Skip to end of metadata
Go to start of metadata

i2b2 offers the following approaches for debugging installation errors.

1 - Webclient XML Log

The webclient XML log shows errors that occur in client/server messaging in a user-friendly interface and should often be the starting point for debugging.

  1. Verify the debug log is turned on. Make sure debug: true appears in i2b2_config_data.js in the webclient installation (see Step 3 of the Web Client Install Guide for an example of the correct file).
  2. Now, the webclient will have a Message Log button in the upper right corner of the screen.

The Message Log allows users to view debug messages if the webcient is in debug mode. This shows the XML messages that pass between the client and server. The Message Log can be opened via the link in the upper right corner of the screen, or via any of the Show XML Message Stack buttons (which will open a filtered view showing only messages relevant to the view from which it was selected). Debug mode can be enabled by an administrator, by modifying the i2b2_config_data.js file.

2 - Server Logging

This is a good second step in debugging, as it shows the detailed errors and warnings that occur on the server. It is the most detailed method, though it also tends to be verbose.

In Wildfly 10 the server logging configuration is defined in the standalone.xml file. By default JBoss has included two handlers; One for logging to the console and another for logging to a file. In order to maximize the speed of your server and to prevent running out of space our recommendation is to have the level of logging set to a low level such as INFO.

Steps to Edit Logging Level

1. Go to the following directory:
2. Open the standalone.xml file to edit its contents.
3. The handlers are in the urn:jboss:domain:logging: subsystem
5. Verify the level name for the console-handler is INFO. Change it if necessary.
<subsystem xmlns="urn:jboss:domain:logging:7.0">
            <console-handler name="CONSOLE">
                <level name="INFO"/>
                    <named-formatter name="COLOR-PATTERN"/>

6. Save the changes and close the file.


If you need to troubleshoot an issue you can set the level to DEBUG. Remember to return it to INFO when you are done.

Troubleshooting Logging

If you are having trouble with this logging approach, try this alternative:

  • In



3 - Webclient Javascript Log

If the error is happening in the client, enabling the Javascript log can be a helpful approach.

  1. In the webclient directory, edit default.htm and comment out line 30, which reads: <script type="text/javascript" src="js-ext/firebug/firebugx.js"></script>
  2. Reload the page, open the javascript console in your web browser and watch for errors. (This process varies by browser. Here is, for example, the method for viewing Javascript errors in Chrome.

4 - Other Approaches

  1. POSTing REST messages. It is possible to POST requests directly to the server, which allows more detailed debugging of REST messages than the webclient offers. Postman is a useful, free tool for this. See
  2. Eclipse Server Logging. It is possible to run the i2b2 server interactively in Eclipse, set breakpoints, and monitor the log output from within the application. In brief, the approach is:
    1. Prerequisites: a local installation of the i2b2 server, and an install of Eclipse with the i2b2 source code checked out (from Git) in a project.
    2. Install the JBOSS tools in Eclipse
    3. Click the server icon in the upper right corner, and set up Wildfly 14 (or whatever version you are using).
    4. Optional: to support breakpoints, rebuild i2b2 with  debugging turned on. In each cell's build.xml, search for the compile target and set debug to true (e.g., <javac destdir="${classes}" optimize="${javac.opt}" debug="true"> ). Then rebuild and redeploy each cell using the ant plugin for Eclipse.

  • No labels