Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.10
-
None
Description
Fix obvious bug in Cluster::timerDrop, it calls the wrong function.
On one occassion this has been seen to cause a cluster broker to go into an infinite loop sending itself timer-drop messages.
There's no know way to reproduce but by inspection of the code the problem and the fix are obvious and trivial.