Make FRM to finally distribute the work orders 82/1182/1
authorGiovanni Meo <gmeo@cisco.com>
Fri, 13 Sep 2013 15:06:08 +0000 (17:06 +0200)
committerGiovanni Meo <gmeo@cisco.com>
Fri, 13 Sep 2013 15:14:08 +0000 (17:14 +0200)
commitb8da7c5be9812ce23d54536771225d88df271769
treefca847d13dce95003b884fe47c4af2f3a9cb489e
parent1391bea690d42096f4ff2056c939882c5b3ca833
Make FRM to finally distribute the work orders

- Transformed frm.{workOrder|workStatus} caches to be transactional,
as a stop gap to an issue we have run into.
- The transformation of FRM caches in transactional opens an issue
where if used in a context of a transaction the FRM updates will not
travel in the cluster. We use the frm.{workOrder|workStatus} caches as
a way to synchronize operations hence this communications need to
happens also before the transaction commits. To avoid then this
chicken-and-egg problem we are forcing the distributeWorkOrder
business logic to execute off a different thread just to avoid to be
held by the transaction.
This is a stop gap solution till we caracterize and fix the
non-transactional cache issue seen

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Change-Id: I8e8dd3f38f037dc62252ea1e271e0972e32019f0
opendaylight/forwardingrulesmanager/implementation/src/main/java/org/opendaylight/controller/forwardingrulesmanager/internal/ForwardingRulesManager.java