-
Notifications
You must be signed in to change notification settings - Fork 43
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
Calling deleteMessagePushStatus() getting 404 #57
Comments
Anybody? |
are you setting a timeout on your message that you place on the queue? (if not the default is still 60 seconds) if could be possible after the first consumer does a GET if 60 seconds(timeout) passes the message ends up back on the queue and is processed by a 2nd consumer. the first consumer sends the delete request which gets received successfully and the second consumer gets a 404 when it attempts a delete. |
So, we create a queue for each message (push) and then queue a message. The exact code is like:
Total time from creating the queue and adding the message to trying to delete it is fast. Basically, as long as it takes Iron.io to send the message to the push endpoint. One of the first things the push endpoint does, is delete the message and queue. So let's call it less than 250ms once Iron.io sends the message to the push endpoint. |
Recently we've been seeing an error when deleting/acknowledging an IronMQ message.
Response is a
404
with:Initially we thought we must be calling
deleteMessagePushStatus()
multiple times, but after checking our code, there is only a single call.What is happening?
The text was updated successfully, but these errors were encountered: