504 gateway timeouts

[Wade Girard]

The version that is on the ubuntu servers was 1.10.xx. I just updated it to

nginx version: nginx/1.13.8

And I am still having the same issue.

How do I "Try to flush out some output early on so that nginx will know
that Tomcat is alive."

The nginx and tomcat connection is working fine for all requests/responses
that take less than 60 seconds.

On Wed, Dec 27, 2017 at 4:18 PM, Igal @ Lucee.org <igal at lucee.org> wrote:

> On 12/27/2017 2:03 PM, Wade Girard wrote:
>
> I am using nginx on an ubuntu server as a proxy to a tomcat server.
>
> The nginx server is setup for https.
>
> I don't know how to determine what version of nginx I am using, but I
> install it on the ubuntu 1.16 server using apt-get.
>
> Run:  nginx -v
>
>
> I have an issue that I have resolved locally on my Mac (using version 1.12
> of nginx and Tomcat 7) where requests through the proxy that take more than
> 60 seconds were failing, they are now working.
>
> What seemed to be the fix was adding the following to the nginx.conf file
>
> proxy_connect_timeout       600;
>
>         proxy_send_timeout          600;
>
>         proxy_read_timeout          600;
>
>         send_timeout                600;
>
> in the location section for my proxy.
>
>
> However this same change in the ubuntu servers has no effect at all.
>
> Try to flush out some output early on so that nginx will know that Tomcat
> is alive.
>
> Igal Sapir
> Lucee Core Developer
> Lucee.org <http://lucee.org/>
>
>
>


-- 
Wade Girard
c: 612.363.0902
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20180104/d23f7bc1/attachment.html>