Reverting the FRM WorkOrder caches to NON_TRANSACTIONAL 15/1315/1
authorMadhu Venugopal <vmadhu@cisco.com>
Fri, 20 Sep 2013 13:56:18 +0000 (06:56 -0700)
committerMadhu Venugopal <vmadhu@cisco.com>
Fri, 20 Sep 2013 13:56:18 +0000 (06:56 -0700)
commit19a34ba9057d07bfbcfb491786ffeb91f5b2c318
tree2eb24d6b68e816f06ff178585e8e9acf43801de1
parent1b88ac1cf4cca6c7b5b371f3d11ef50e8dc9aacf
Reverting the FRM WorkOrder caches to NON_TRANSACTIONAL

After Giovanni's recent hashCode fix, most of the cache issue issues are resolved and it also renders itself to making
FRM WorkOrder back NON_TRANSACTIONAL. Also reverted the need to have a seperate thread to handle this processing.
Now it is back to normal and how it is supposed to be.

Change-Id: I0abbe66ea0ec7203ef306bc73d848112110f6460
Signed-off-by: Madhu Venugopal <vmadhu@cisco.com>
opendaylight/forwardingrulesmanager/implementation/src/main/java/org/opendaylight/controller/forwardingrulesmanager/internal/ForwardingRulesManager.java