Affects Version/s: 0.8, 0.10
Fix Version/s: 0.11
The assumption in Timer appears to be that no thread will ever throw from TimerTask::fire(). In practice however few of the implementations of that method in the broker take any measures to ensure that is the case. If code called on a timer thread throws there is therefore the risk of the broker terminating (I have observed such a case for example on the management periodic processing).
It would probably be advisable to add some generic protection for this.
|Field||Original Value||New Value|
|Assignee||Gordon Sim [ gsim ]|
|Summary||No exception handling for manay timer tasks in broker||No exception handling for many timer tasks in broker|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Fix Version/s||0.11 [ 12316272 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|17h 20m||1||Gordon Sim||05/Apr/11 11:08|