-
-
Notifications
You must be signed in to change notification settings - Fork 364
IFailFastChecker
Mogens Heller Grabe edited this page Dec 6, 2018
·
1 revision
IFailFastChecker
is what Rebus uses after having caught an exception, to decide whether it makes sense to retry delivery of the message.
By default, the fail fast checker will return true for exceptions that implement IFailFastException
(which is an empty marker interface).
This means that you can make Rebus fail fast on certain exception types by adding that interface to your exceptions.
If you don't want to do that, or if you can't (e.g. if the exception type is not defined by you), then you can extend the behavior by adding a decorator. Check out Fail fast on certain exception types for an example on how to do this.
Basic stuff
- Home
- Introduction
- Getting started
- Different bus modes
- How does rebus compare to other .net service buses?
- 3rd party extensions
- Rebus versions
Configuration
Scenarios
Areas
- Logging
- Routing
- Serialization
- Pub sub messaging
- Process managers
- Message context
- Data bus
- Correlation ids
- Container adapters
- Automatic retries and error handling
- Message dispatch
- Thread safety and instance policies
- Timeouts
- Timeout manager
- Transactions
- Delivery guarantees
- Idempotence
- Unit of work
- Workers and parallelism
- Wire level format of messages
- Handler pipeline
- Polymorphic message dispatch
- Persistence ignorance
- Saga parallelism
- Transport message forwarding
- Testing
- Outbox
- Startup/shutdown
Transports (not a full list)
Customization
- Extensibility
- Auto flowing user context extensibility example
- Back off strategy
- Message compression and encryption
- Fail fast on certain exception types
Pipelines
- Log message pipelines
- Incoming messages pipeline
- Incoming step context
- Outgoing messages pipeline
- Outgoing step context
Prominent application services