Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
vicks_mq wrote:
Consider a production scenario, an application which send update message has set expiry to 30 mins and the receiving application is down and they are working to bring it up, but in the meantime the Sending application messages start getting expired in 30 mins one by one, we would not want that scenario.
So we need that at will we can save from expiry atleast all the new update messages coming so that we don't lose them.
By design, any message that has expiry is disposable and ephemeral. The putting app has made a deliberate choice:
Here is an amount of time that MQ can keep this message while it is being delivered or waiting for consumption. If this time is exceeded, it is safe to discard the message.
The message doesn't have any lasting value to the business. Usually it can be regenerated if required. It should be idempotent.
If you care about the message being consumed, DO NOT use expiry. _________________ Glenn
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum