Code Review / controller.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 27b8125) | patch
Timeout ForwardingRulesManager workOrder 65/1365/2
authorGiovanni Meo <gmeo@cisco.com>
Mon, 23 Sep 2013 20:02:40 +0000 (22:02 +0200)
committerGiovanni Meo <gmeo@cisco.com>
Tue, 24 Sep 2013 13:59:19 +0000 (15:59 +0200)
commitb1a1182db907b19fe986d3cd18146b7842fc58c9
tree681ef7df398cb238985f583b8eee159964209752tree | snapshot
parent27b812571223282220de1b4b065a3d13bdb45daacommit | diff
Timeout ForwardingRulesManager workOrder

- Before this patch is an FRM request was submitted and no answer was
received by a remote controller, that would indefinitively stuck the
caller, clearly a bad practice. This patch is introducing a default
timeout of 30 second (very bad scenario) and a log.error is being
raised if that happens.
- Cleaned workMonitor cache on workStatus coming back or timeout.
- Make timeout tunable via system properties

Change-Id: I59ac402b30101e3cf1cf1b1beacf03fbc9add6c9
Signed-off-by: Giovanni Meo <gmeo@cisco.com>
opendaylight/forwardingrulesmanager/implementation/src/main/java/org/opendaylight/controller/forwardingrulesmanager/internal/FlowEntryDistributionOrderFutureTask.java diff | blob | history
opendaylight/forwardingrulesmanager/implementation/src/main/java/org/opendaylight/controller/forwardingrulesmanager/internal/ForwardingRulesManager.java diff | blob | history
OpenDaylight controller