[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 10/2/17 6:24 PM: ------------------------------------------------------------------- talking to pcameron in #openshift-dev we found out that the haproxy in the router-pod had processed the instruction. The timeout really is set to the timeout that's specified in the annotation. {code} [adietish@localhost jbosstools-openshift]$ oc project default [adietish@localhost jbosstools-openshift]$ oc rsh router-1-z56wl sh-4.2$ cat haproxy.config {code} {code} .... # Plain http backend backend be_http:node:nodejs-mongo-persistent mode http option redispatch option forwardfor balance leastconn timeout server 2h {code} So there's no explanation so far to why the haproxy would answer with a gateway error. He told me to talk to bbennett was (Author: adietish): talking to pcameron in #openshift-dev we found out that the haproxy in the router-pod had processed the instruction. The timeout really is set to the timeout that's specified in the annotation. {code} [adietish@localhost jbosstools-openshift]$ oc project default [adietish@localhost jbosstools-openshift]$ oc rsh router-1-z56wl sh-4.2$ cat haproxy.config {code} {code} .... # Plain http backend backend be_http:node:nodejs-mongo-persistent mode http option redispatch option forwardfor balance leastconn timeout server 2h {code} So there's no explanation so far to why the haproxy would answer with a gateway error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)