Controlling Visual Query timeout

Depending on the complexity of the query structure and the volume of data involved, Visual Queries can take a long time to run. By default, i2 Analyze automatically terminates any Visual Query that runs for more than four hours, but you are free to increase or reduce this setting.

About this task

In the i2 Analyze configuration settings, the VisualQueryTimeoutMinutes property controls how long a Visual Query can run before the server stops it and reports that it failed.

If you know that your Visual Queries usually take less than four hours to run, then reducing the timeout can let you know sooner that something might be wrong. Alternatively, if you know that you have long-running queries that take more than four hours, you can increase the timeout.

To follow this procedure in a deployment that provides high availability, you must complete each step on every Liberty server in your environment before you move to the next step.

Procedure

To change the Visual Query timeout setting:

  1. Using a text editor, open the DiscoServerSettingsCommon.properties file. You can find this file in the following location: toolkit\configuration\fragments\opal-services\WEB-INF\classes.

  2. Edit the value of VisualQueryTimeoutMinutes.

  3. Save and close the file.

Redeploy i2 Analyze to update the application with your changes:

  1. In a command prompt, navigate to the toolkit\scripts directory.

  2. Stop Liberty:

    setup -t stopLiberty

  3. Update the i2 Analyze application:

    setup -t deployLiberty

  4. Start Liberty:

    setup -t startLiberty

What to do next

Run a selection of Visual Queries and verify that under normal circumstances, none of them causes a timeout error. If necessary, increase the timeout setting until no predictable timeout errors occur.