Pattern Catalog
| Message Expiration |
Pattern Catalog | |
| Site Home • Patterns Home • Table of Contents |
My application is using Messaging. If a Message’s data or request is not received by a certain time, it is useless and should be ignored.
How can a sender indicate when a message should be considered stale and thus shouldn’t be processed?
Set the Message Expiration to specify a time limit how long the message is viable.
Once the time for which a message is viable passes, and the message still has not been consumed, then the message will expire. The messaging system’s consumers will ignore an expired message; they treat the message as if it where never sent in the first place. Most messaging system implementations reroute expired messages to the Dead Letter Channel, while others simply discard expired messages; this may be configurable.
...Related patterns: Dead Letter Channel, Guaranteed Delivery, Invalid Message Channel, Message, Messaging, Publish-Subscribe Channel, Request-Reply
For a full description of the pattern see:
 | Enterprise Integration Patterns
Gregor Hohpe and Bobby Woolf ISBN 0321200683 650 pages Addison-Wesley |
| Home • Patterns • Table of Contents |  Previous Next  |
 | © 2003 • Bobby Woolf • All rights reserved. |