Re: 504 error in relatively small query

Doesn't the query keep running anyway?  I often have long jobs which
timeout in the browser but run to completion (unless I terminate them in
the Monitor).  When this is anticipated , I make sure the job writes output
to a database file rather than (only) to return HTML

Chris Wallace

On Mon, Mar 13, 2023 at 3:00 PM Ralph Corrigan <[email protected]> wrote:

> Thanks Olaf, yes we are. I'll take a look at that...
>
>
> Ralph
>
>
> On 13/03/2023 14:35, [email protected] wrote:
>
> This returns absolutely fine up to ~1200 items in the subsequence $ref but
> by the time we get closer to 2000 (and more) this returns a 504 gateway
> time-out error in roughly 60s.
>
>
> Are you running eXist behind a proxy like nginx?  I've had 504s created
> from nginx frontend proxies.  In that case, you need to increase timeouts
> in the nginx config.
>
> Olaf
>
>
> _______________________________________________
> Exist-open mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
> _______________________________________________
> Exist-open mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

_______________________________________________
Exist-open mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/exist-open