Jazz behind a reverse proxy
We ran the initial jazz instance v1.0.1.1 successfully behind a reverse proxy (running apache - Server version: Apache/2.2.4 on RedHat AS release 4).
Following the upgrade to v2 it takes up to 5 mins to display the logon screen and between 5 to 10 mins to display the initial page. Once logged on performance is reasonable. The vhosts entry is: NameVirtualHost 10.23.12.199:443 <VirtualHost> ServerName <name> SSLEngine on SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP SSLCertificateFile <name> SSLCertificateKeyFile <name> DirectoryIndex index.html index.htm index.shtml SSLProxyEngine On ProxyRequests Off ProxyVia On ProxyPreserveHost On ProxyPass / https://<ip>:443/ ProxyPassReverse / https://<ip>:443/ Has anyone else run jazz behind a reverse proxy? |
2 answers
Hi,
Yes, we are running RTC through a reverse proxy on jazz.net, using similar rules. I don't recall seeing any performance issues like this, but since we are self-hosting, we didn't go straight from 1.0.1.1 to 2.0, but adopted each milestone instead. A few questions.. - Was this only on the first startup after upgrade or does the problem still happen? - Does it happen if you bypass the reverse proxy and point your browser directly at the jazz server? - Does it happen with the eclipse-based client as well, or only the Web UI? - Could you try using firebug (or equivalent) to see which request is the slow one? Thanks, Curtis |
|
Curtis,
We get similar (slow) performance irrespective of whether we use IE, firefox or client / web UI. Before upgrading to 2.0 performance was acceptable, but now the time taken to display the 1st screen takes 5-10 mins, after authenticating continually. If you connect directly to the server (no reverse proxy) performance is fine. We re-located the server to an ADSL connection (again no reverse proxy) and performance was again acceptable. It is only when traffic gets routed via the reverse proxy do we get a significant depredation in performance. Mike |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.