Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle 504 GATEWAY_TIMEOUT #53

Open
awm33 opened this issue Jul 13, 2015 · 2 comments
Open

Handle 504 GATEWAY_TIMEOUT #53

awm33 opened this issue Jul 13, 2015 · 2 comments

Comments

@awm33
Copy link

awm33 commented Jul 13, 2015

Sometimes, when long polling a queue, I get a 504 error after waiting. I'm not sure if this is expected behavior, but it bubbles up to the queue get() function as an Error with no way of telling what kind of error, so an if () could check for it

@BradRuderman
Copy link

Can you share your polling code? Also does your error look like:
{"code":"ETIMEDOUT","errno":"ETIMEDOUT","syscall":"connect"}
Because I get those randomly as well.

@peebles
Copy link

peebles commented Feb 6, 2016

I too am occasionally getting ETIMEDOUT from either a dequeue or a delete. The NodeJS default http request timeout is 2 minutes. In 2 minutes I can get a lot of messages backed up. What I want is to be able to set my own timeout, more like 30 seconds, that gets passed to request( options, ... ) in iron_core.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants