Tasks #119
Handle exceptions in dispatch callbacks
| Status: | Resolved | Start date: | 09/09/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | J. Wienke | % Done: | 100% | |
| Category: | C++ | |||
| Target version: | - |
Description
Neither not catching exceptions in called user-functions nor using catch(...) is an elegant way, but these exceptions must be handled in any case. Maybe there are compiler-specific functionalities to generate a backtrace of an exception at runtime. Otherwise I would propose a configuration property to either completely crash on an exception (development usage) or generate a maximally meaningful log message (production use).
Associated revisions
add a variable to ParticipantConfig to maintain the error strategy
refs #119
- Modify ParallelEventDispatchingStrategy to use the ErrorStrategy.
- Add tests and a death test facility
refs #119
pass error strategy to event processing strategy from listener
fixes #119
History
#1 Updated by J. Wienke about 13 years ago
- Assignee changed from S. Wrede to J. Wienke
#2 Updated by J. Wienke about 13 years ago
- Status changed from New to In Progress
#3 Updated by J. Wienke about 13 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset r788.