此内容没有您所选择的语言版本。
Chapter 14. Configuring OpenShift connection timeout
By default, the OpenShift route is configured to time out HTTP requests that are longer than 30 seconds. This may cause session timeout issues in Business Central resulting in the following behaviors:
- "Unable to complete your request. The following exception occurred: (TypeError) : Cannot read property 'indexOf' of null."
- "Unable to complete your request. The following exception occurred: (TypeError) : b is null."
- A blank page is displayed when clicking the Project or Server links in Business Central.
All Business Central templates already include extended timeout configuration.
To configure longer timeout on Business Central OpenShift routes, add the haproxy.router.openshift.io/timeout: 60s annotation on the target route:
- kind: Route
apiVersion: v1
id: "$APPLICATION_NAME-rhdmcentr-http"
metadata:
name: "$APPLICATION_NAME-rhdmcentr"
labels:
application: "$APPLICATION_NAME"
annotations:
description: Route for Business Central's http service.
haproxy.router.openshift.io/timeout: 60s
spec:
host: "$DECISION_CENTRAL_HOSTNAME_HTTP"
to:
name: "$APPLICATION_NAME-rhdmcentr"For a full list of global route-specific timeout annotations, see the OpenShift Documentation.
