(Migrated) 504 Gateway TIme-out on long-running service

(This message has been automatically imported from the retired mailing list)

Hello,

We have developed a service that reads a message queues (ibmmq) or files,
then call other Zato SIO services that updates a PostgreSQL database and
finally calls SOAP services.
When reading a large file, everything is going well but I hit some timeout
and I receive ‘504 Gateway Time-out’ when invoking it from the admin
interface.

Is it the case to increase main.gunicorn_timeout ?

Thanks and Best Regards,
Guilherme

Thanks!
Btw after this I have decided to just call the plain http channel using
curl.

[]s,
Guilherme

On Fri, May 29, 2015 at 4:07 PM, Dariusz Suchojad dsuch@zato.io wrote:

On 29/05/15 21:04, Guilherme Monteiro wrote:

Is it the case to increase main.gunicorn_timeout ?

Please instead increase the timeout between web-admin and the
load-balancer, or load-balancer and servers:

https://zato.io/docs/web-admin/load-balancer/gui.html#frontend-config

Does it time out after 15 seconds? If so, this is it - you can increase
it to 100000 for instance (in ms).

On 29/05/15 21:04, Guilherme Monteiro wrote:

Is it the case to increase main.gunicorn_timeout ?

Please instead increase the timeout between web-admin and the
load-balancer, or load-balancer and servers:

https://zato.io/docs/web-admin/load-balancer/gui.html#frontend-config

Does it time out after 15 seconds? If so, this is it - you can increase
it to 100000 for instance (in ms).