Hi All,

We have setup a BPS 320 cluster on QA cloud (1 manager and 2 worker
nodes)with nginx LB.In this setup when we keep the setup idle and try to
login back using admin console UI, We are getting a 504 Gateway time out.
Once restart the manager node we were able to login back and we observed
this incident several times.
Is this a known issue(Google says this happens due to network delays) ? or
Do we need to have any specific config on nginx configuration to avoid this.

We are running with below nginx config and adding proxyPort and proxyName=
mgt.bps.com to the catalina-server.xml.

Mgr 1 :192.168.48.113
Wrk 1: 192.168.48.114
Wrk 2: 192.168.48.115
nginx :192.168.48.115


http {


# load balancing among the worker nodes - HTTP
upstream wrk.bps.com {
            server 192.168.48.114:9763;
            server 192.168.48.115:9763;

}

server {
          listen 80;
          server_name wrk.bps.wso2.com;
          location / {
                      proxy_pass http://wrk.bps.com;
          }
}

# load balancing among the worker nodes - HTTPS
# To configure load balancing for HTTPS instead of HTTP, just use “https”
as the protocol.
upstream ssl.wrk.bps.com {
          server 192.168.48.114:9443;
          server 192.168.48.115:9443;
}

server {
          listen 443;
          server_name wrk.bps.wso2.com;
          ssl on;
          ssl_certificate /etc/nginx/ssl/wrk.crt;
          ssl_certificate_key /etc/nginx/ssl/wrk.key;
          location / {
                      proxy_pass https://ssl.wrk.bps.com;
          }
        }

server {
    listen 443;
    server_name mgt.bps.com;
    ssl on;
    ssl_certificate /etc/nginx/ssl/mgt.crt;
    ssl_certificate_key /etc/nginx/ssl/mgt.key;
    location / {
        proxy_pass https://192.168.48.113:9443/;
        }
    }



-- 
Asanka Vithanage
Senior Software Engineer -QA
Mobile: +94 0716286708
Email: [email protected]
WSO2 Inc. www.wso2.com
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to