Service times out

The OpenPages service times out.

Symptoms

The user interface shows that OpenPages is processing a request but the process does not complete. Or, a process stops unexpectedly.

For example, FastMap processing stops unexpectedly or the process continues to run but does not complete. You might see errors in the <OP_HOME>/wlp-usr/servers/<server_name>Server<#>/logs/messages.log file about FastMap temporary files.

Or, when you create a new profile, the process runs but then you see Unexpected error in your browser. The Java™ console shows 504 (Gateway Time-out).

Causes

The process didn't finish within the timeout value.

Resolving the problem

If you use an external load balancer, such as HAProxy, to route network requests to OpenPages, configure a long enough timeout value (such as 10 minutes). Some OpenPages operations, such as importing with FastMap, can take longer than other operations.

As a Red Hat® OpenShift® cluster administrator, reset the client and server timeout values for the load balancer and then restart it.

For example, if you have the HAProxy load balancer:

  1. On the load balancer node, edit the /etc/haproxy/haproxy.cfg file. In the defaults section, change the values for timeout client and timeout server from 1m to 10m.
  2. Run the following command to restart HAProxy: 
    systemctl
restart haproxy