[CONTROLLER-1071] Clustering: RuntimeEx thrown from client DCL kills the DCL actor Created: 16/Dec/14 Updated: 06/Jan/15 Resolved: 06/Jan/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Tom Pantelis | Assignee: | Tom Pantelis |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 2517 |
| Priority: | Normal |
| Description |
|
If a client AsyncDataChangeListener implementation throws an unexpected runtime exception, the exception gets propagated from the DataChangeListener actor to akka. This essentially kills the DataChangeListener actor or akka disables it as it won't receive any more data changed events. The DataChangeListener actor should catch and log RuntimeExceptions thrown from the client DCL to prevent one from stopping all subsequent data changed events. |
| Comments |
| Comment by Tom Pantelis [ 16/Dec/14 ] |
|
Submitted https://git.opendaylight.org/gerrit/#/c/13668/ to master |
| Comment by Tom Pantelis [ 30/Dec/14 ] |
|
Cherry picked to helium: https://git.opendaylight.org/gerrit/#/c/13835/ |